Luxor Says Commander Was Hijacked—And an Attacker Collected Bitcoin From Redirected Hashrate
• November 15, 2026 7:24 pm • CommentsA Bitcoin mining fleet can contain thousands of machines, but every one of them still follows a few basic instructions: where to send its computing work and where the resulting rewards should go.
For a group of Luxor customers, someone changed those instructions.
Luxor says an attacker used its Commander fleet-management software to redirect customer hashrate to the OCEAN mining pool for a limited period. The company says just over a dozen client accounts were affected, Commander was patched within two hours, and no customer data was leaked or exfiltrated.
The incident did more than create a scary dashboard anomaly. An on-chain transaction shows that the attacker-controlled payout address later received 0.0809 Bitcoin from an OCEAN block.
Crypto Watch Desk reconstructed the sequence using the companies’ public posts, OCEAN data and the block’s coinbase transaction. Its reporting draws a sharp line between Bitcoin’s network and the fleet-control software used by industrial miners.
The first public alarm appeared at 03:08 UTC, when CoreX identified the OCEAN pool and a specific payout address. The host later reported roughly 13 exahashes per second pointed at that address before the redirected power fell toward 100 petahashes per second by 06:40 UTC.
OCEAN’s public figures showed the pool’s total hashrate jump sharply during the same window. Later that day, the pool found block 975,995 and its normal share-based payout process sent 8,088,977 satoshis to the address named in the alert.
Luxor then confirmed that the redirect had run through Commander, affected just over a dozen client accounts, and lasted for a limited window. The company said no data was exfiltrated, promised full compensation, and said a full post-mortem would follow.
The first warning came from the operators watching their machines.
CoreX Hosting raised the alarm early Sunday after miners began pointing to OCEAN and using a single unfamiliar payout address. That detail was concrete enough for other operators to check their own pool settings instead of waiting for a broad security advisory.
Just a heads up, there is a big miner hack going on as we speak. Miners are being pointed at @ocean_mining with BTC address bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr .
— CoreX Hosting (@CoreX_Hosting) November 15, 2026
The key distinction is between Bitcoin and the software around it. No wallet was drained and no consensus rule was broken.
The attacker instead changed the destination for work produced by real mining machines.
That can still be expensive. Hashrate is the revenue-producing output of a mining fleet.
If it is silently pointed at somebody else’s payout address, the owner keeps paying for electricity and operations while another party receives the economic benefit.
Public estimates placed the redirected power near 13 exahashes per second and the affected fleet near 64,000 machines. Those figures have not been independently confirmed, and Luxor’s statement did not endorse the machine count.
What Luxor did confirm is that more than a dozen customer accounts were affected through Commander.
Luxor says it contained the redirect and will make customers whole.
Last night our internal monitoring alerted us to an unauthorized redirect of hashrate through Commander. Our on-call engineering team jumped on it right away.
Impact: just over a dozen client accounts. Affected machines were pointed to a different pool for a limited window. No…
— Luxor Technology (@luxor) November 15, 2026
The company said internal monitoring detected the redirect, Commander was patched within two hours, and affected machines were restored toward their original pool settings.
Every affected client is supposed to be paid as though the redirected hashrate had mined normally. That promise limits the direct financial damage if it is fulfilled.
It does not answer the central technical question: how did the attacker gain enough control to change fleet settings?
The company said Commander was operating normally after the patch and that a fuller post-mortem would follow. Until that arrives, claims about the precise attack vector should be treated as unverified.
The blockchain recorded a payout before the investigation was finished.
OCEAN uses a share-based payout system. The redirected machines accumulated shares in the pool’s payout window even though they did not personally find the next block.
When OCEAN found block 975,995, its coinbase transaction sent 8,088,977 satoshis to the address CoreX had identified. That is 0.08088977 BTC.
The payment is a useful piece of evidence because it does not depend on a company’s press release. The transaction is public, the destination matches the reported address, and the amount closely matched OCEAN’s projected reward for the shares in its window.
It also exposes the operational risk in a modern mining stack. The Bitcoin protocol can behave exactly as designed while vulnerable management software redirects the work of physical machines.
For mining operators, the immediate lesson is unglamorous and important: verify pool URLs and payout addresses at the machine level, watch for sudden changes in pool-side hashrate, rotate credentials held by remote-management tools, and keep independent production records.
Luxor’s compensation pledge may close the accounting gap. The promised post-mortem will have to close the trust gap.
Join the conversation!
We have no tolerance for comments containing violence, racism, profanity, vulgarity, doxing, or discourteous behavior. If a comment is spam, instead of replying to it please click the icon below and to the right of that comment. Thank you for partnering with us to maintain fruitful conversation.
