Approximately 64,000 Bitcoin mining machines were reportedly compromised over the November 14–15, 2026 weekend, allowing attackers to redirect an estimated 13 exahashes per second (EH/s) of computing power to the OCEAN mining pool. The incident involved unauthorized changes to mining pool configurations, redirecting computational resources away from their legitimate destinations and toward a Bitcoin payout address controlled by the attackers. Mining infrastructure provider CoreX Hosting first reported the suspicious activity after discovering that equipment under its supervision had been reassigned to another pool without authorization.
OCEAN’s reported hashrate briefly approached 50 EH/s before declining toward 40 EH/s. The diverted computing power subsequently fell to approximately 100 petahashes per second, indicating that most affected machines had been restored or disconnected. Luxor Technology confirmed on November 15 that attackers exploited its Commander fleet-management platform, affecting just over a dozen customer accounts. The company has not independently confirmed the reported 64,000-machine estimate or the total diverted hashrate.
Luxor Confirms Commander Security Breach and Promises Compensation
Luxor said its internal monitoring systems detected unauthorized redirection of mining activity, prompting an immediate response from its engineering team. The company patched the identified vulnerability within two hours of detection and began restoring affected machines to their original pool configurations. Luxor emphasized that the incident was isolated to Commander and did not affect its mining pool or LuxOS firmware products. It also stated that no customer data had been leaked or extracted from its systems.
Chief Executive Nick Hansen characterized the intrusion as involving a sophisticated artificial intelligence-enabled attack technique, although the company has not disclosed the specific mechanism used. Luxor promised to compensate affected clients for the redirected computing power as though their machines had continued mining normally. The company said Commander was operating normally following the security update and that customers did not need to take additional action. A detailed post-incident report is expected, but no publication date has been announced.
Blockchain Records Contradict Initial Claims of Zero Attacker Revenue
Early reports indicated that the attackers had failed to earn Bitcoin because OCEAN had not produced a block during the initial diversion. However, subsequent blockchain analysis challenged that conclusion. On November 15, OCEAN mined Bitcoin block 975995, which included a payment of 0.08088977 BTC, worth approximately $5,250 at the time, to the address identified as receiving the diverted mining rewards. Further reporting indicated that the address subsequently received a second payment, bringing the reported total to approximately 0.162 BTC, or $10,500.
The payments demonstrate that the attackers received mining rewards despite earlier claims that the operation had generated no proceeds. OCEAN’s payout mechanism can distribute rewards for previously submitted mining work even after the contributing machines have disconnected. The incident did not compromise Bitcoin’s underlying consensus protocol or demonstrate that attackers gained access to miners’ cryptocurrency wallets. Instead, it exposed vulnerabilities associated with centralized software used to manage large mining fleets.
The distinction is significant because controlling pool configurations can redirect mining revenue without taking direct control of blockchain transactions. Although Luxor has committed to reimbursing affected operators, the incident highlights the financial risks posed by compromised management infrastructure and the importance of securing remote access to industrial-scale cryptocurrency mining equipment.
