- The Luxor hack let attackers send other operators’ Bitcoin miners to the OCEAN pool through the company’s Commander software.
- Bitcoin’s blockchain, Luxor’s own pool and its LuxOS firmware were not affected.
- The attacker’s address was still paid after the redirection had been stopped.
- Luxor says it will pay affected customers as if their machines had mined normally.
In the early hours of November 15, attackers got into Luxor Technology’s Commander fleet-management platform and used it to send about 13 EH/s of Bitcoin mining power, roughly 1.4% of the network, to the OCEAN pool and to a payout address they controlled. Luxor confirmed the breach later that day. It said just over a dozen customer accounts were involved and promised to make those customers whole. Bitcoin transaction records show the attacker’s address has since received two OCEAN payouts totaling 0.16202083 BTC, about $10,500, both after the hijack had been contained.
By mining standards that is a small amount. What makes the case worth attention is how the attackers got in: through software that now stands between large ASIC fleets and the people who own them.
Four Hours on the Wrong Pool
CoreX Hosting, which runs mining infrastructure, raised the alarm first after it saw client machines connecting to OCEAN when they were set up for other pools. Its public updates over the night give the clearest record of how long the redirection lasted.
~02:00 UTC Unauthorized redirection reportedly begins
03:08 UTC CoreX Hosting warns of a large-scale mining hijack
03:57 UTC About 13 EH/s still pointed at the attacker’s address
06:40 UTC CoreX says the incident is over, with about 100 PH/s left
17:22 UTC OCEAN finds block 975,995 and pays the attacker’s address
Early reports put the number of affected machines at 64,000. Nobody has published an inventory to back that up. It also sits more easily beside Luxor’s “dozen accounts” than it first appears, because one institutional account in a fleet tool often controls thousands of ASICs.
One Account, Thousands of Machines
Luxor launched Commander in April 2026 for mining operators who were managing pools, firmware and power through separate vendors. It offers real-time monitoring and bulk remote commands across a whole fleet. It also runs on the major manufacturers’ stock firmware, not only on Luxor’s own LuxOS. At launch, Luxor said more than 500,000 machines were running within its ecosystem.
The bulk commands that let an operator retune a site in minutes also let the attackers change two settings on every machine they could reach: the mining pool and the Bitcoin payout address. The miners kept hashing as usual. Nothing broke on site and the hardware showed no faults, but the value of the work went to an address the owners had never heard of. Luxor CEO Nick Hansen called the attack vector “sophisticated” and AI-enabled, warning on X that crypto businesses are now inundated with AI-enabled attacks. The company has not yet said how AI was used in this one.
OCEAN’s design makes it a convenient destination for this kind of scheme. Miners connect to OCEAN using a Bitcoin address as their username, with no account and no identity check. The pool then pays rewards directly to that address inside the block’s coinbase transaction, the first transaction in each block, which creates the newly issued coins. Nothing indicates that OCEAN played any part beyond being the destination. The jump was easy to spot on OCEAN’s own dashboard, where the pool’s hashrate climbed toward 50 EH/s during the night before settling near 40 EH/s.
The Payout That Arrived After the Fix
The first accounts said the attackers got nothing because OCEAN found no block during the hijack. That missed how OCEAN pays out. Its TIDES system credits miners for the shares they submit across a rolling window that covers several blocks (a share is a unit of proof that a miner did work for the pool). Work done during the hijack therefore still counted when OCEAN found block 975,995, and the attacker’s address, bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr, received 2.58% of that block’s reward. A second payment of 0.08113106 BTC followed the same day, bringing the total to 0.16202083 BTC, and as of Sunday evening OCEAN’s dashboard still credited the address with 2.64% of the reward window, so further payouts remain possible until the old work drops out of it.
| Metric | Figure | Status |
|---|---|---|
| Hashrate diverted | ~13 EH/s | Reported by CoreX |
| Machines affected | ~64,000 | Unverified estimate |
| Luxor accounts involved | Just over a dozen | Confirmed by Luxor |
| Payout to attacker | 0.16202083 BTC (~$10,500) | On-chain, two payments |
| OCEAN dashboard figure | ~0.6576 BTC | Estimate, not paid |
Sources: CoreX Hosting, Luxor, PublicAML, mempool.space
Luxor has not published a loss figure. A rough estimate goes like this: at a 3.125 BTC block subsidy, the network issues about 450 BTC a day, so 1.4% of the hashrate earns around 6.3 BTC a day. Four hours of the full 13 EH/s would come to about 1.05 BTC, close to $68,000 at a BTC price of $65,000, before transaction fees. Real losses depend on how long each machine stayed redirected, and Luxor’s promise to compensate customers shifts most of the direct cost onto the company.
Fleet Software Joins the Threat Model
Luxor says it patched the vulnerability within two hours, no customer data left its systems, and its pool and LuxOS firmware were not affected. CoreX spotted the attack from outside the management software, not through it. CoreX caught the hijack because its machines connected to a pool they were never set up for. Any site that relies on a remote-management layer now has a reason to monitor pool destinations and payout addresses independently of that layer. A change to those two settings is exactly what this attack made.
Bitcoin’s mining difficulty fell 9.13% to about 134.82 trillion in its latest adjustment. Difficulty is recalculated every 2,016 blocks based on how fast those blocks were produced. Nothing ties the drop to the hijack, which moved hashrate between pools without taking it off the network. The 13 EH/s also never approached the majority share a 51% attack would need.
Both payouts arrived as coinbase outputs, which Bitcoin’s maturity rule locks for 100 blocks, roughly 17 hours, before they can be spent, so the first becomes spendable at block 976,095 on November 16. The address has not spent anything so far, and anyone watching it on mempool.space will see whether the coins move and where. Hansen has promised a fuller post-incident report on how the attackers got access. Other fleet-software users need that answer to know whether the weakness was specific to Commander.
Credit: Source link
