Imagine owning a Bitcoin mining farm. The machines are running, the electricity bill is yours, and every hash is supposed to earn revenue for your business. Then someone changes one configuration field and points that work at a Bitcoin address you do not control.
The machines do not stop. Bitcoin does not stop. But the economic output is no longer yours.
That is the operational failure Luxor Technology disclosed after an incident during the night of November 14 to 15. The company says attackers used Commander, its remote fleet-management software, to redirect mining power from just over a dozen customer accounts to another pool without permission. Luxor says its engineers patched the tool within two hours, began restoring the original pool settings and will fully reimburse affected customers.
Industry reports put the peak diversion near 13 exahashes per second, or roughly 1.4% of the estimated Bitcoin network hashrate at the time, and describe approximately 64,000 mining machines as affected. Those two figures have circulated widely, but Luxor has not confirmed them in its public statement. They should be treated as estimates until the promised technical post-mortem provides a measured scope.
The target was mining infrastructure, not Bitcoin
This was not an attack on Bitcoin's consensus rules, proof-of-work function or transaction history. The attacker appears to have targeted a control layer used by mining operators.
Mining machines are normally configured with a pool endpoint and an identity that determines where credit for their work goes. Remote-management platforms allow operators to change those settings across large fleets. That is useful when thousands of machines must be monitored, rebooted or moved between pools. It also creates a concentrated control surface: unauthorized access can change the destination of an entire farm's work without touching the hardware or the Bitcoin protocol.
CoreX Hosting raised the first public alert and identified the payout address as bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr. The redirected machines were pointed at OCEAN, whose pool hashrate rose sharply before most of the unauthorized power was recovered. Reports say the address-linked hashrate fell from about 13 EH/s to roughly 100 PH/s within hours.
The incident is closer to changing the bank details on thousands of invoices than to breaking the monetary system that settles them. The work remained valid. The accounting destination changed.
The attacker did get paid
Early coverage said the attacker earned nothing because OCEAN did not find a block while the diverted hashrate was at its peak. That conclusion misunderstood how the pool distributes rewards.
OCEAN uses TIDES, a transparent reward system that tracks submitted shares across a rolling window equal to eight blocks of network difficulty. A miner's shares can therefore remain eligible for portions of later block rewards after the miner disconnects. The machine that finds the winning block is not the only participant paid.
On-chain data confirms four direct coinbase outputs to the flagged address:
- 0.08088977 BTC in OCEAN block 975,995.
- 0.08113106 BTC in block 976,029.
- 0.08106822 BTC in block 976,084.
- 0.08136679 BTC in block 976,097.
Together, those outputs total 0.32445584 BTC as of 12:05 UTC on November 16. The address had no earlier payments, and none of the received bitcoin had moved at that observation time. Additional rewards were still possible while the diverted shares remained inside OCEAN's TIDES window.
The roughly 0.66 BTC visible in early pool estimates was not the amount already paid. It represented prospective rewards associated with work still in the window and depended on OCEAN finding more blocks before those shares aged out. The chain, not the estimate, is the correct measure of realized payouts.
Small proceeds, large warning
The amount is modest relative to the scale of the reported diversion. But profitability is not the main lesson. The incident demonstrates that mining revenue can be stolen without compromising a private key, moving a treasury wallet or attacking Bitcoin itself.
For mining operators, the relevant security perimeter includes:
- fleet-management accounts and administrative credentials;
- API keys and automation tokens;
- pool endpoints and payout identities;
- access logs and alerts for bulk configuration changes;
- independent monitoring that compares expected and observed pool hashrate.
Large operators should treat changes to pool and payout settings like changes to bank settlement instructions: require strong authentication, narrow privileges, multiple-party approval where practical and immediate out-of-band alerts.
Luxor has confirmed the software channel involved, but the precise entry point remains unresolved publicly. Chief executive Nick Hansen described the incident as an AI-enabled attack, without publishing technical evidence showing how artificial intelligence was used. That attribution should remain provisional until the company releases its post-mortem.
Decentralized settlement still depends on operational security
OCEAN was designed to reduce pool custody and make reward allocation auditable. Its direct coinbase payouts are precisely why the suspicious outputs can be verified on-chain. We previously covered OCEAN's role in the debate over mining decentralization.
But transparency does not prevent an attacker from submitting valid work under an address they control. Bitcoin correctly settled the work it was instructed to settle. The failure occurred before consensus, in the software used to tell machines where and for whom to mine.
That distinction matters. The episode is not evidence that Bitcoin's proof of work was broken. It is evidence that industrial mining inherits the same identity, access-control and software-supply risks as every other networked infrastructure business. A decentralized protocol can remove trusted intermediaries from settlement. It cannot remove the need to secure the systems that connect real companies to it.
This publication is market analysis, not a recommendation to buy or sell.
