In this article5 sections
Attackers used Luxor Technology’s Commander management software to switch the mining pool and payout settings on machines across more than a dozen client accounts, AMBCrypto reported. Mining host CoreX Hosting put the scale at roughly 64,000 Bitcoin miners and 13 EH/s of hashrate, redirected to the OCEAN mining pool. Luxor disclosed the incident on X on November 15, saying internal monitoring had flagged the unauthorized redirect the night before.
The affected machines mined for the other pool “for a limited window,” Luxor said, and the company patched Commander within two hours before moving machines back to their original settings. Luxor also said every affected client would be paid in full for the redirected hashrate, as if it had mined normally. Bitcoinist reported that affected operators kept paying electricity costs while their rigs worked for someone else’s benefit.
Also read: Luxor Raises $16M to Expand AI Compute Business
Key facts
- CoreX Hosting reported about 64,000 miners and 13 EH/s of hashrate were compromised; Luxor confirmed just over a dozen client accounts were affected.
- Luxor patched Commander within two hours and said Luxor Pool and LuxOS were not impacted, with no data leaked or taken.
- Attackers redirected hashrate to OCEAN; the attacked hashrate fell to about 100 PH/s while OCEAN’s spiked to 48.8 EH/s before settling near 40 EH/s.
- An address identified by CoreX Hosting received three block-reward payments totaling roughly 0.243 BTC, valued at about $15,700 at the time of Bitcoinist’s reporting.
- Luxor CEO Nick Hansen described the intrusion as involving a sophisticated AI-enabled attack vector.
Rewards moved despite the patch
Bitcoinist reported that the attackers did receive actual mining rewards, citing three block-reward payments totaling about 0.243 BTC sent to an address CoreX Hosting initially identified. OCEAN allows previously submitted mining work to remain eligible for a share of later block rewards over a rolling period, which helps explain how payments can arrive after machines have been switched back. Luxor said the reconfiguration window was limited and that the attacker failed to mine a block, meaning no block reward was earned.
Unchained reported that Luxor has promised a full post-mortem but had not yet published one, and that the company did not name the pool receiving the hashrate in its disclosure. Bitcoinist identified OCEAN as the destination. The reports differ in emphasis on scale: CoreX Hosting’s 64,000-miner figure describes the machines involved, while Luxor’s own count describes customer accounts.
Hansen points to AI-enabled attacks
Hansen tied the breach to what he called a sophisticated AI-enabled vector, according to Unchained, and said in a post on X that “you trust us with your fleet, and we need to be better.” He said crypto businesses now face continuous probing by abliterated AI models with safety restrictions removed, and that Luxor has bought dedicated GPUs to run such models for defensive testing. Bitcoinist reported that Hansen did not explain precisely how AI was used or how attackers gained access, and that the company paused much of its new feature development to harden its infrastructure.
AMBCrypto noted that customers discovered their pool information had changed without their knowledge, and that some onlookers compared the episode to an attack on Hiveon days earlier. The weak point was not the mining hardware but the management layer sitting above it.
Why it matters
Mining management platforms set where hashrate points and who gets paid, so controlling them gives an attacker access to future revenue without touching a single wallet or rig. That risk sits outside the exchange and custody breaches that usually dominate crypto security coverage. For hosting providers and their clients, the incident raises questions about access controls, change monitoring and how quickly unauthorized pool switches are detected. Luxor’s compensation pledge addresses the immediate losses, but confidence in remotely managed fleets depends on the security work Hansen described.
What to watch
Luxor has promised, but not yet published, a full post-mortem on the breach. Its contents, along with any detail on how attackers entered Commander and whether the security changes hold, will determine how quickly clients rebuild trust in the software.
Reported by AMBCrypto.
Sources: AMBCrypto, Bitcoinist, Unchained

