If one login can reconfigure thousands of rigs at once, whoever holds it owns your hashrate. Luxor's own fleet software just showed what that looks like, and the bill was small only because the break-in was caught fast.
Luxor, the bitcoin mining pool and software company, confirmed over the weekend that attackers got into Commander, its fleet-management platform, and pointed the hashrate of just over a dozen client accounts at a different mining pool. According to The Block, Luxor's on-call engineers patched the hole within two hours, and the company says no customer data was leaked or exfiltrated.
The intrusion began at about 6 p.m. Pacific time on Saturday, November 14, TFTC reported. The redirected machines were sent to OCEAN, a rival pool, and TFTC, citing figures from CoreX Hosting, put the diverted fleet at roughly 64,000 machines and 13 exahashes per second. That is around 1.4% of the whole bitcoin network, taken over by changing a setting.
One note on naming: some roundups call the product Luxor Fleet. Luxor's own description, as relayed by The Block, calls it Commander, and says the compromise was limited to that product. Its mining pool, its LuxOS firmware and its other services weren't touched.
Not much. TFTC's reading of the chain shows the payout address tied to the redirected hashrate received about 0.162 BTC across two coinbase payouts, and as of November 16 those coins hadn't moved. OCEAN pays out proportionally rather than letting miners keep a block they find, so even 13 EH/s pointed at it couldn't produce a jackpot. TFTC says no block was solo-mined during the window.
Bitcoin's BIP-110 soft fork enters its mandatory signaling window around August 7, with miner support at roughly 0.31% of total hashrate. The proposal would ban Ordinals inscription data for one year, but with Adam Back, Michael Saylor, and Jameson Lopp all opposed, a chain split looks more likely than a clean upgrade. - bitcoin BIP-110 fork signaling status - cryptocurrency protocol soft fork deadline
The miners who lost out are the ones to watch. For roughly two hours their machines worked for someone else, and the customers' own pool accounts got nothing for it. Luxor says every affected client will be compensated in full for the redirected hashrate, and that it has begun restoring machines to their original pool settings. Commander is running normally, and users don't need to do anything, according to the company.
Luxor has also promised a post-mortem. It hasn't published one yet.
The AI claim deserves skepticism
CEO Nick Hansen told The Block that "anyone running any sort of substantial business, especially in crypto, is inundated with AI-enabled attacks," and described this one as a "sophisticated AI-enabled vector." He didn't say how AI was used. TFTC notes that the technical mechanism remains unpublished and unverified.
Frankly, treat that as a claim, not a finding. "AI-enabled" could mean automated scanning for a weak spot, or it could be a label for an ordinary stolen credential. Until Luxor shows its work, the only part of the story you can build a security plan on is the part nobody disputes: a management layer sat between attackers and tens of thousands of machines, and getting through it was enough.
That's the real lesson for anyone running rigs, hosting machines for others or building tools on top of them. A fleet dashboard exists to change settings on every device at once. TFTC's analysis makes the same point, arguing that one compromised credential hands an attacker the same mass-reconfiguration power the operator has. This time the attacker used it to switch the pool address. A more patient one could have pushed bad firmware or throttled machines instead.
What to check on your own rigs
You can't audit Luxor's code, but you can audit your own exposure, and a few checks take an afternoon. Turn on multi-factor authentication for every account that can edit pool settings, and use hardware keys where the platform supports them. Set an alert on your pool dashboard for any drop in your own worker count or hashrate, since that was the first visible symptom here. Keep a record of your intended payout and pool addresses somewhere the management software can't edit, so you can compare in minutes. And ask any hosting or software provider whether a change to pool configuration needs a second approval, because most don't.
Luxor isn't the only name in this game, and its timing is awkward. The firm raised $16 million last month from CMT Digital and others, The Block reported, and said it bought bare-metal GPUs to run its own security models. Hansen says most feature work is now paused while the company hardens its systems.
A firmware bug in Coldcard hardware wallets caused devices to silently use a weak software random number generator since March 2021, producing seeds with roughly 40 bits of entropy instead of 128. An attacker exploited this to drain 594 BTC worth $38.3 million from 500 single-signature wallets in 25 minutes on July 31, 2026. Coinkite has issued... - coldcard firmware bug bitcoin drain - hardware wallet security vulnerability investigation
The broader mining sector is already under strain. MARA Holdings sold 13,597 BTC, about 40% of its stack, after September 30 for roughly $1.1 billion, using $750 million to repay its bitcoin-backed loans, according to its quarterly shareholder letter and coverage of it. Margins are thin enough that a two-hour hijack across a dozen accounts is a real cost to someone.
Luxor hasn't said which clients were hit or how many machines each one ran. Those numbers will probably come with the post-mortem.
Also read: Solana mainnet full node runs on a tablet over 5G, and Yakovenko says 'We did it' • Coinone says hackers breached its customer-support contractor MetaM and saw IDs and passwords • stUSDT begins winding down with $8.6 million left of its $2.3 billion peak
This article is posted in Crypto News, check it out for more related stories.
Join the discussion
Almost there. Sign in and your reply posts straight away.



