Luxor Technology confirmed on 15 November that an unauthorized change ran through Commander, its fleet-management software. The change redirected the mining power of just over a dozen client accounts to a different pool. Luxor patched Commander within two hours of detecting it and said the fault was isolated to that one tool. It promised to pay every affected client as if their machines had mined normally.
- The news: Luxor says an unauthorized redirect of client mining power ran through its Commander software, which it patched within two hours.
- The figure: A Bitcoin address tied to the incident received two OCEAN payouts totaling about 0.162 BTC, worth roughly $10,500, on 15 November.
- Next: Luxor has promised a full post-mortem and full compensation, with no payment date, total amount or calculation method yet.
Commander Sits Above the Miners
Commander is fleet-management software that mining operators use to run their machines. Luxor's product page says it can change pool settings on thousands of miners in a single operation. That is why an attack on it behaves differently from a protocol or key breach: the attacker does not need to touch each rig. Luxor said the problem was isolated to Commander and that Luxor Pool and LuxOS were not affected. It also said no data was leaked or exfiltrated from its systems.
Luxor said Commander is now operating normally and that users need to take no action.
Hansen Calls It an 'AI-Enabled Vector'
CEO Nick Hansen said the compromise began around 6 p.m. Pacific time on Saturday, 14 November. In a post on X, he said it affected a subset of Commander customers, through what he called a "sophisticated AI-enabled vector." He has not said how AI was used.
"At this moment, anyone running any sort of substantial business, especially in crypto, is inundated with AI-enabled attacks," Hansen wrote. "This does not seem to be slowing down; rather, it's speeding up as models get better and more attackers enter the arena."
He said Luxor has put most of its feature work on hold to harden its security. It also bought its own GPUs to run unrestricted open-weight AI models for defense. He urged other operators of similar services to do the same: "I urge anyone running a similar service to do the same. It's your only defense in this new AI-powered dark forest."
The Onchain Trail: Two Coinbase Payouts
Mining host CoreX Hosting flagged a Bitcoin address it tied to the redirect. CoreX reported about 13 exahashes per second going to it, then said that address's hashrate had fallen to about 100 petahashes per second. At 03:57 UTC on 15 November, roughly two hours after the redirect began, CoreX wrote that "the attack is on-going, the hacker pool address is still sitting at 13EH." It added: "I am changing miners back as I can."
On OCEAN's dashboard, that address shows zero blocks found but records a payout of about 0.0809 BTC. The matching onchain transaction confirms the payment. Under OCEAN's TIDES reward system, miners receive a proportional share of rewards for work recorded in the pool's reward window when any pool miner finds a block. An address does not need to find a block itself to be paid. OCEAN is a noncustodial Bitcoin mining pool launched in 2023 with financial backing from Jack Dorsey.
Update (16 November): The address tied to the redirect holds exactly two transactions, both coinbase outputs. Block 975,995 at 17:22:50 UTC on 15 November paid 0.08088977 BTC. Block 976,029 at 22:54:00 UTC paid 0.08113106 BTC. That leaves a balance of 0.16202083 BTC, worth about $10,512 at the $64,883 bitcoin price CoinGecko recorded on 16 November.
What Luxor Has Not Disclosed
Before Luxor went public, reports suggested that about 64,000 mining machines representing an estimated 13 EH/s had been redirected toward OCEAN. Those figures remain independently unverified. Luxor has not disclosed the number of machines, the total hashrate or the money involved. The exact mechanism of the "AI-enabled vector" is not published.
Whether the compromise was a vendor-side failure or a client-side one is also unresolved in public. CoreX said it had "isolated what I think is the program used," pointing at something running on the operator side rather than at a breach of Luxor's platform.
Luxor said affected clients would receive an email that day with more details. It gave no payment date, total compensation amount or calculation method for the refunds. The promised post-mortem has not been published.


