BitcoinWorld Luxor confirms Commander breach after 13 EH/s diverted Bitcoin mining technology firm Luxor said its Commander mining-management platform was breached, allowing an unauthorized r
BitcoinWorld
Luxor confirms Commander breach after 13 EH/s diverted
Bitcoin mining technology firm Luxor said its Commander mining-management platform was breached, allowing an unauthorized redirect of hashrate across more than a dozen client accounts. The company disclosed the incident after mining infrastructure provider CoreX Hosting raised the alarm on Nov. 15 that equipment was being pointed at the OCEAN pool with rewards assigned to a single Bitcoin address, Cryptoslate reported.
Luxor confirmed that an unauthorized redirect of hashrate was made through its Commander platform over a limited window, affecting more than a dozen client accounts. The company patched the platform within two hours and has promised to compensate affected customers, but has not confirmed the reported scale of the diversion.
Key facts
- CoreX Hosting flagged the redirect on Nov. 15, naming the Bitcoin address bc1qphuk…pcddrr as the payout destination.
- GalaxyMind estimated that about 64,000 machines and 13 EH/s were redirected from around 8 p.m. Central Time on Nov. 14, with CoinSpect putting the computing power at roughly 1.5% of Bitcoin’s global hashrate.
- OCEAN data shows three payments totaling 0.24308905 BTC to the named address between Nov. 15 and Nov. 16, including 0.08088977 BTC in block 975995.
- Luxor CEO Nick Hansen blamed a “sophisticated AI-enabled vector” and said the attack began around 6 p.m. Pacific time on Nov. 14.
- CoreX said it restored affected miners, and later declared the incident over after computing power tied to the suspicious address fell to about 100 PH/s.
How the diversion was spotted and what the blockchain shows
CoreX’s alert at 03:08 GMT on Nov. 15 named the destination address. At 17:25 GMT, mempool.space recorded a confirmed transaction funding that address with 8,088,977 satoshis — 0.08088977 BTC — with no recorded spending. That output was part of the coinbase transaction in block 975995, timestamped 17:22:50 GMT on Nov. 15 and labelled OCEAN by mempool.space.
The record establishes that a reported destination became a recorded reward recipient. It does not establish who controls the address, nor prove which incident shares generated the payment. OCEAN’s TIDES reward system lets previously submitted work qualify for payments from later blocks, so rewards can keep arriving after hashing stops. Eligibility does not guarantee another payment.
CoreX said it believed it had isolated the program behind the unauthorized changes. It reported restoring machines to their original configurations, then declared the episode closed once the suspicious address’s associated hashrate collapsed.
Luxor’s account: two-hour patch and a promise to pay
Luxor said its own monitoring caught the redirect and that affected machines were pointed to a different pool for a limited window. The firm stated no data was leaked or exfiltrated, patched Commander within two hours, and began returning machines to their original pools. It pledged full compensation for the redirected computing power.
Hansen apologised to affected customers and warned that crypto businesses face a rising tide of automated attacks, saying abliterated models run around the clock probing every exposed surface and expand almost instantly through any weakness. He said Luxor had bought dedicated GPUs to run its own modified models for defensive testing and suspended much of its new feature development to harden infrastructure.
Luxor has not disclosed how Commander was compromised and has not confirmed GalaxyMind’s estimates of machine count or hashrate.
Why it matters
The incident targeted the management layer rather than the mining hardware itself, which means an operator’s rigs can work and burn power while earnings flow somewhere else — a cost hit that shows up only after payouts diverge. Luxor’s promise of compensation covers its own clients, but the breach raises a question every hosting customer faces: who holds the authority to change pool settings, and how quickly would an unauthorised change be noticed?
Hansen’s warning also frames this as a security-cost problem for the sector, with one vendor diverting engineering resources from product work into defensive hardening.
What to watch
Luxor has committed to a full post-mortem, which should establish the entry point, the true scale of the disruption and whether all the reported computing power ran through its compromised platform. Watch whether those findings reconcile with GalaxyMind’s 64,000-machine estimate.
Frequently Asked Questions
How much hashrate was affected by the Luxor Commander incident?
Luxor has not confirmed the scale. GalaxyMind estimated that roughly 64,000 machines and 13 EH/s were redirected, and CoinSpect said that represented about 1.5% of Bitcoin’s global hashrate.
What did Luxor say caused the breach?
Luxor CEO Nick Hansen attributed the compromise to what he called a sophisticated AI-enabled vector and said the attack started around 6 p.m. Pacific time on Nov. 14. The precise entry point has not been disclosed.
Did the attackers receive Bitcoin rewards?
Yes. OCEAN data shows three payments totaling 0.24308905 BTC to the address named in CoreX’s alert between Nov. 15 and Nov. 16, including 0.08088977 BTC in block 975995.
Was customer data taken from Luxor’s systems?
Luxor stated that no data was leaked or exfiltrated from its systems during the incident.
What should miners take away from this incident?
Because redirected machines kept consuming electricity while rewards went elsewhere, operators should review who can change pool configuration on their equipment and monitor payout addresses for unexpected edits.
This post Luxor confirms Commander breach after 13 EH/s diverted first appeared on BitcoinWorld.