Luxor Says a Dozen Accounts Were Hit, a Host Counted 13 EH/s

Luxor confirmed on Sunday that mining power running through Commander, the tool its customers use to manage fleets of bitcoin machines, was redirected without authorization to the OCEAN pool. The statement went up on its X account at 17:25 UTC and put the damage at "just over a dozen client accounts". Hosting firms and the outlets following them described something far larger: roughly 64,000 machines and about 13 EH/s of hashrate pointed at a pool nobody had chosen. Luxor gave no machine count and no hashrate figure of its own. Nobody has reconciled the two.
When it started, and who noticed
Nick Hansen, Luxor's chief executive, put the start at "Around 6:00p PDT yesterday" in a post the same day, which lands near 01:00 UTC on Sunday. Crypto Briefing gives roughly 8 p.m. Central Time on Saturday, an hour later in UTC. Neither account explains the gap. The first outside sign came from CoreX Hosting, which spotted unauthorized changes to pool settings on machines it runs. By 03:57 UTC it was posting that the redirect was still live and that it was switching miners back one at a time. Crypto Briefing says similar pool changes had surfaced in the days before, without naming who saw them.
What the payout address actually earned
Two figures circulate and they sit a factor of four apart. news.bitcoin.com put the suspected address at an estimated 0.65761026 BTC, sourced to Mononaut, a mempool.space developer, who read it off OCEAN's dashboard and noted no confirmed incoming transactions on chain. cryptonews.net instead traced two settled coinbase outputs to the address CoreX published: 0.08088977 BTC from block 975,995 and 0.08113106 BTC from block 976,029 some five hours later, 0.16202083 BTC in all, worth about $10,512 at the price it used. One is shares credited on a dashboard, the other is bitcoin that settled. Neither account mentions the other.
"I apologize. You trust us with your fleet, and we need to be better," Hansen wrote.
Whether any blocks were found is unsettled in the same way. Crypto Briefing wrote that no blocks were mined and the payout address received no payments. cryptonews.net identified two OCEAN blocks that paid it. OCEAN has published no notice about any of it.
The mechanism is still not public
Luxor has not said how the redirect was achieved. Its statement describes "an unauthorized redirect of hashrate through Commander" and goes no further. No product version, no credential or session detail, no CVE. cryptonews.net wrote that Luxor confirmed the vector, which the statement it quotes does not support. Hansen called it "a sophisticated AI-enabled vector" and said abliterated models now run around the clock against any sizeable crypto business, looking for a crack. That attribution is his alone. CoreX pointed elsewhere, saying it was fairly sure it had isolated the program involved, which reads as an operator-side problem. A mining bug in Bitcoin Core came with a full write-up last month. This one has a promise of a post-mortem and no date.
Numbers that nobody has lined up
OCEAN's own hashrate is the one place the scale is visible, and the readings vary. TFTC saw the dashboard spike near 50 EH/s. Crypto Briefing watched it climb to about 50 and settle around 40. cryptonews.net recorded 40.35 EH/s on Monday morning, and relayed CoreX's reckoning that 13 EH/s on one address was 1.39% of a 934 EH/s network. That percentage comes from one outlet. CoreX's diverted capacity later fell to about 100 PH/s.
What operators are left holding
Luxor says Commander was patched within two hours and that it began restoring machines to their original pool settings. CoreX was still working through its fleet hours later. The company says no data left its systems, that the pool and LuxOS were untouched, and that every affected client will be paid in full for the redirected hashrate as if it had mined normally. None of that is auditable from outside. Exposed credentials in crypto infrastructure have cost this industry more than hashrate before. The useful check is a dull one. Read the pool endpoint and payout address off the machine, not off the panel that is supposed to be setting them.
Read also: Paraguay's $350 Million Miner Power Contracts Expire at End of 2027