GetChain News
中简 中繁 EN
GetChain News
Toggle sidebar

Security/Hacker

News linked to both this project and an event.

Ocean Mining denies involvement in Luxor software attack

Bitcoin mining pool operator Ocean Mining stated that its systems were unaffected and it was not involved in the attack on Luxor's Commander software. The incident resulted in the unauthorized redirection of hashrate from Luxor and its clients to other mining pools, including Ocean Mining. (Bitcoin.com News)

Luxor Rotates Keys and Hardens Infrastructure to Counter AI Attacks

Bitcoin mining service provider Luxor is hardening its infrastructure by rotating keys, updating kernels, and pinning dependencies, while pausing most new feature development. CEO Nick Hansen is calling on companies operating similar services to take the same measures.Luxor previously stated that attackers used Commander to briefly redirect the hash rate of more than ten customer accounts to other mining pools. The company patched the vulnerability within two hours and promised full compensation to affected customers. (Decrypt)

Operations have resumed normally, and Luxor's Commander has completed its vulnerability fix

According to monitoring by Luxor Technology, Commander has resumed normal operations. Luxor Technology stated that after the earlier attack, engineers fixed the vulnerability within two hours and began restoring the affected mining machines to their original pool settings.

Luxor CEO: Crypto companies are facing AI-driven attacks

Luxor CEO Nick Hansen stated that following attacks on some Commander customers, the company has suspended development of most new features to strengthen security measures.

Luxor CEO: Attack was carried out through sophisticated AI-assisted vectors; will conduct a post-mortem and apologize to customers

The Luxor CEO stated that the attack was carried out through sophisticated AI-assisted vectors, and that the company will conduct a post-mortem and apologize to customers. (Bitcoin.com News)

The Bitcoin protocol and consensus rules remain intact; the hashrate of approximately 64,000 mining machines was redirected

Odaily report: According to OCEAN monitoring, approximately 64,000 Bitcoin mining machines were taken control of, and about 13 EH/s of hashrate was redirected to the OCEAN mining pool. The incident began at around 8 PM Central Time that evening. OCEAN reported that its hashrate once rose to approximately 50 EH/s, then stabilized at around 40 EH/s; the diverted hashrate later dropped to approximately 100 PH/s, and most of the affected mining machines were pulled back or went offline within a short period. All redirected output flowed to a payment address controlled by a single attacker, but the attacker did not mine any blocks, and the address received no payment; the lost income of the miners of the hijacked machines cannot be recovered. Hosting provider CoreX Hosting was the first to notify the operator, saying it discovered unauthorized changes to the mining pool settings of the affected machines. One operator said the entire mining operation was affected and suspected the entry point was the mining machine fleet management software Luxor Commander, but this connection has not been confirmed. In the days before November 14, there had already been reports of unauthorized changes to mining pool settings, and the incident may not be isolated. The Bitcoin protocol and consensus rules were not compromised; what failed was the operational software connecting mining companies and hardware.

Approximately 64,000 Bitcoin mining machines hijacked, 13 EH/s hashrate redirected to OCEAN mining pool

Odaily reports: According to monitoring by Bitcoin News, approximately 64,000 Bitcoin mining machines were reportedly hijacked, involving 13 EH/s of hashrate. The mining machines' hashrate was redirected to the OCEAN mining pool, with proceeds designated to be paid to Bitcoin addresses controlled by the attackers. The attack reportedly began around 8 PM Central Time on November 14. The OCEAN dashboard showed its hashrate briefly approaching 50 EH/s before falling back to approximately 40 EH/s. CoreX Hosting was the first to raise the alarm, stating that mining machines had been switched to other mining pools without authorization. One affected operator claimed that their entire mining farm was hijacked and pointed to Luxor's Commander mining machine management software as the source of the security incident; other operators reported similar unauthorized mining pool changes that had occurred several days earlier. CoreX subsequently stated that the attack appeared to have ended, with the hijacked hashrate dropping from 13 EH/s to approximately 100 PH/s. The attackers reportedly failed to mine any Bitcoin blocks during the hijacking and therefore received no block rewards; affected miners permanently lost the opportunity to earn Bitcoin during the attack period. The full scope of the security incident, as well as whether Luxor Commander was compromised, has not yet been independently confirmed.