Luxor says attacker redirected client mining hashrate to Ocean
Luxor said an attacker used its Commander fleet software to redirect the hashrate of just over a dozen client accounts to the Ocean pool on November 14. Engineers patched the flaw within two hours, and the firm has promised to pay affected clients in full.
By Zain
Published · 5 min read
Bitcoin mining services firm Luxor said an attacker broke into its Commander software late on November 14 and redirected the mining hashrate of just over a dozen client accounts to a rival pool. Engineers closed the hole within two hours.
Luxor confirmed the breach in a public statement on Sunday, November 15. Nick Hansen, the company's chief executive, said the intrusion started around 6:00 p.m. Pacific time on Saturday, a little after 01:00 UTC. "Around 6:00p PDT yesterday, a subset of Commander customers were compromised, through a sophisticated AI-enabled vector," Hansen wrote. Luxor is one of the better-known names in Bitcoin mining services, and runs its own pool alongside the fleet tools it sells.
What the attacker did
Start with the basics. A Bitcoin miner runs specialized computers that race to add the next block to the chain. Most miners do not go it alone. They join a pool, combining their computing power, called hashrate, and share the rewards by how much work each one puts in. The pool sends each payout to the account its machines report to.
Commander is Luxor's fleet-management tool. A client uses it to watch and control many machines from one dashboard, including the setting that tells each rig which pool to mine for. Change that setting, and the machines go to work for someone else. That is what happened here. The attacker pointed the affected clients' hashrate at Ocean, a separate Bitcoin pool launched in 2023 with backing from Jack Dorsey.
Ocean itself has not been accused of any role. A pool is just the address where redirected work shows up, and being the endpoint of a switch does not mean the pool arranged it or knew about it. The rewards that landed there, by the accounts of on-chain watchers, appeared to go unclaimed.
The money side is simple. When the hashrate was redirected, the pay flowed to the Ocean destination instead of the people who owned the rigs. The machines kept running. They kept drawing power too, so the rightful owners were covering the electricity while someone else stood to collect the reward. Luxor said it caught the change, patched Commander, and began switching the affected miners back to their original settings. The pool and the firmware it sells, called LuxOS, were not touched. No data was taken. Luxor said Commander is now running normally, and that affected clients need take no action of their own.
What Luxor has not said
Luxor gave one hard number: just over a dozen accounts. It has not said how many machines that covered, how much hashrate moved, or how much the attacker earned before the rewards stopped. Those gaps matter, because the bigger figures circulating elsewhere are not the company's.
Early third-party reports put the diverted capacity near 13 exahashes per second, drawn from about 64,000 machines. Luxor has confirmed neither. One hosting firm later said the unauthorized hashrate had dropped to roughly 100 petahashes, a small fraction of that. On-chain watchers pointed to an Ocean address holding under one bitcoin in estimated rewards, and said the funds appeared to sit uncollected. The gap between a dozen accounts and 64,000 machines is the difference between a contained slip and a serious breach, and only Luxor can close it. Treat the rest as provisional until the company publishes its own count.
Why Luxor calls it an AI attack
Hansen framed the breach as part of a wider pattern. He said any sizable business, crypto firms most of all, now faces a steady stream of automated, AI-driven probing. "Abliterated models are running 24/7 against your entire surface," he wrote, describing tools stripped of their safety limits and aimed at finding weak points without rest.
That claim is worth holding at arm's length. Luxor has not yet published how the attackers got in, so the AI-enabled label rests on the chief executive's account alone. Taking over a management account to redirect hashrate is not a new trick. It predates the current wave of AI tooling by years. The promised post-mortem should show whether the method here was genuinely new or an old attack dressed in fresh language.
Hansen did not hide behind the framing. "I apologize," he wrote. "You trust us with your fleet, and we need to be better." Luxor said every affected client will be paid in full for the lost work, credited as if the machines had mined normally for their rightful pool.
What to watch
The post-mortem is the next real test. It should say how the attacker reached Commander, whether a stolen credential or a software flaw was to blame, and what Luxor has changed since. Watch for the compensation to actually land, and for any affected client to dispute the firm's account of the scope.
There is a broader lesson for miners. Tools that let one dashboard steer thousands of machines save a lot of time, and they also create a single point of failure. When the dashboard falls, everything behind it can fall with it. The incident is a prompt to check who can change a pool setting, and how fast anyone would notice if they did.
Luxor's AI framing will draw its own scrutiny. Blaming a breach on smart software can read as a way to deflect from a basic lapse, and some engineers will see it that way until the post-mortem shows the detail. Others will point out that automated probing is a real and growing problem, whatever turns out to have happened here.
Frequently asked
What is Luxor Commander?
Commander is Luxor's fleet-management software for Bitcoin miners. It lets an operator watch and configure many machines from a single dashboard, including which mining pool each machine works for. Luxor said the November 14 attack abused Commander to change those pool settings for just over a dozen client accounts.
Did Luxor lose customer coins or data?
No. Luxor said no data was leaked or stolen, and the attacker did not reach client funds. The harm was redirected mining rewards for just over a dozen accounts. Luxor has promised to pay those clients in full for the work their machines did, as if the hashrate had mined normally.
Was the Ocean pool involved in the attack?
There is no evidence that Ocean took part. The attacker chose Ocean as the destination for the redirected hashrate, so the rewards showed up there. On-chain watchers reported the funds appeared to sit unclaimed. Being the endpoint of a redirect does not mean a pool arranged it or knew about it.
Sources, and what is behind them
- Luxor statement on the Commander security incident, Luxor (November 15, 2026)Press report
- Luxor hit by AI-enabled attack that redirected client hashrate, says vulnerability patched, The Block (November 15, 2026)Press report
- Luxor Confirms Bitcoin Mining Hack and Reveals AI-Enabled Attack, Bitcoin.com News (November 15, 2026)Press report
- Luxor CEO warns of rising AI-enabled cyberattacks after mining hijack, Crypto Briefing (November 15, 2026)Press report