Morning Edition · Monday, November 16, 2026Published at 12:44 AM EST · New York
Luxor fixed the flaw within two hours and will repay just over a dozen affected accounts, though early unconfirmed reports put the diverted power as high as 13 exahashes per second, well above the smaller scope Luxor itself later described.

Luxor, a bitcoin mining services company, said an attack on Commander, its software for managing fleets of mining machines, redirected the mining power of more than a dozen client accounts to OCEAN, a separate mining pool. Luxor said it will repay affected clients in full. According to The Block, Luxor's monitoring caught the unauthorized redirects and its engineers patched the flaw within two hours. The company said the breach was confined to Commander, no other services were affected, and users do not need to take any further action.
Nick Hansen, Luxor's chief executive, blamed a "sophisticated AI-enabled vector" but has given no technical detail on how artificial intelligence was used or what the flaw was. He said automated, AI-driven probing of company systems is constant and accelerating. TFTC and other outlets note that the AI claim is the company's own description and has not been independently verified. Luxor has promised a detailed report and, according to reports, has paused most feature development to harden its security.
Reports of the scale conflict. Early unconfirmed reports described about 64,000 machines producing an estimated 13 exahashes per second (EH/s) pointed at OCEAN. Over the same period OCEAN's visible mining power rose to about 50 EH/s and then settled near 40 EH/s. CoreX, a mining operator, later said the compromised power had fallen to about 100 petahashes per second. Estimates of the attacker's proceeds also differ. One report cites about 0.162 bitcoin reaching the payout address. Another cites a dashboard figure of about 0.657 bitcoin in shares. A third found no confirmed incoming transactions. Reports place the start of the intrusion either around 6 p.m. Pacific time or around 8 p.m. Central time on November 14.
Based on current reporting, the root cause was unauthorized use of privileged control software. Neither Bitcoin's protocol nor OCEAN's code was at fault. Fleet-management software is allowed to set each machine's pool address and worker credentials. Whoever controls that software decides where the mining power goes and who gets paid for it. Industrial miners need the same remote control to switch large fleets on and off quickly, which is the basis of proposals that flexible mines absorb curtailed Scottish wind power. The small payout compared with the reported diverted power means the attacker earned little during the window. Luxor has not said what it believes the attacker wanted.
Part of a tracked trend
Losses Move to Components That Worked as Designed
A growing share of DeFi losses will come not from buggy contract code but from components behaving exactly as specified — oracle forwarders, validator signature sets, governance votes and other trusted off-contract inputs — so audits and bug bounties scoped to on-chain code keep missing the failure surface, and protocols will be repeatedly forced to extend review, scope and monitoring to their privileged operational infrastructure.
Start a discussion in Townsquare.
More from this edition
If the attack really was "AI-enabled," Luxor shares the blame with a threat facing the whole industry rather than a flaw in its own code, and that helps it keep the industrial miners who pay for Commander. Rival vendors and self-hosted fleet software gain if clients start to doubt third-party control of pool settings.
Independent outlets confirm the core event (The Block, Bitcoin.com), which is unauthorized pool redirects through Commander. The scale and cause are not confirmed. The figure of 13 exahashes per second (EH/s) is still an unverified early estimate set against Luxor's count of "just over a dozen" accounts, and the AI attribution rests only on the word of Nick Hansen, Luxor's chief executive, who has offered no technical evidence.
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
The exposure sits with industrial miners who hand pool settings to third-party management software. One credential or interface flaw in that software can move many machines at once, so the software becomes a single point of control over mining power that sits outside the pool-share figures used to measure concentration. Luxor wants the episode framed as a new class of AI-driven threat, which spreads responsibility beyond its own code. Clients will want a root cause they can audit. This would not be the first time attackers hijacked pool-management software. What is new is that the attack reportedly moved mining power in bulk without touching any key that holds coins. There is an earlier case: in 2014, Dell SecureWorks researchers reported an internet routing hijack (a BGP hijack) that rerouted miners' connections to attacker-run pools, and the industry responded with authenticated pool connections over years rather than months. The likelier outcome is that large miners will require signed or two-person approval for pool changes, and some will move fleet control onto self-hosted systems within months. That depends on Luxor's report showing that the flaw sat in Commander's own access controls. The read is wrong if the report shows that client-side credential theft caused the breach, because that would put the fix on customers rather than on the software.
What to watch
Observations to monitor, not financial advice.
Synthesized from: Polylog editors · The Block · Crypto Briefing · TFTC · TradingView / Crypto Briefing · MLQ.ai · CryptoSlate
Comments
1Nov 16, 5:44 AM
If the diversion really approached 13 EH/s, OCEAN's measured hashrate should show a matching spike during the attack window, which would test the early reports against Luxor's smaller stated scope.