0x182320131823…18232016
Luxor Confirms Hashrate Hijack Through Commander Platform
Luxor confirmed attackers redirected hashrate through its Commander platform, affecting about a dozen accounts. CEO Nick Hansen calls it an AI-enabled attack; full post-mortem is pending.
Outputs
Luxor confirmed unauthorized hashrate redirection through Commander beginning ~6 p.m. PDT, Nov. 14, 2026
Just over a dozen client accounts affected; engineers patched Commander within about two hours
CEO Nick Hansen attributed the intrusion to a "sophisticated AI-enabled vector"; no technical findings published yet
Suspected destination address accrued an estimated 0.65761026 BTC in shares; no confirmed payouts on-chain
Unverified early reports claimed ~64,000 machines / 13 EH/s redirected; CoreX Hosting later measured ~100 PH/s
Luxor Technology has confirmed that attackers redirected customer mining equipment through its Commander fleet-management platform, in a security incident the company says began around 6 p.m. Pacific time on Saturday, Nov. 14, 2026. The Seattle-based mining services firm disclosed the breach in a statement issued Sunday, describing the intrusion as a "sophisticated AI-enabled vector" while acknowledging that technical findings establishing the method of attack have not yet been published.
The confirmed scope, according to Luxor, was narrow: just over a dozen client accounts, with affected machines pointed to a different mining pool for a limited window. The company maintains that no data was stolen. "Impact: just over a dozen client accounts. Affected machines were pointed to a different pool for a limited window. No data was leaked or exfiltrated from our systems," the team wrote on X. That figure, it should be noted, does not establish the number of physical machines involved — a dozen fleet accounts can control thousands of devices.
How did Luxor respond?
Luxor's internal monitoring systems detected unauthorized modifications to mining pool configurations on Saturday night. "Last night our internal monitoring alerted us to an unauthorized redirect of hashrate through Commander. Our on-call engineering team jumped on it right away," the company said.
Engineers patched Commander within roughly two hours, the firm stated, before beginning the slower process of restoring affected machines to their original configurations. Luxor has committed to full financial restitution: "Compensation: every affected client will be paid in full for the redirected hashrate, as if it had mined normally." CEO Nick Hansen, who said the episode had made "the last 12 hours ... pretty rough," apologized directly to customers. "I apologize. You trust us with your fleet, and we need to be better," he wrote. Luxor also says the compromise was confined to Commander; its mining pool and LuxOS firmware were unaffected, and affected customers will receive further details by email.
The company has promised a comprehensive post-mortem. Until that document appears, the "AI-enabled" characterization remains an assertion rather than an evidenced finding — no technical mechanism has been published.
What did on-chain data show?
Before Luxor's confirmation, reports circulating late Saturday suggested that approximately 64,000 machines, representing an estimated 13 exahash per second (EH/s), had been redirected toward Ocean, the noncustodial Bitcoin mining pool launched in 2023 with backing from Jack Dorsey. Those figures remain unverified, and Luxor's disclosure of roughly a dozen accounts cannot be reconciled with them on current evidence.
Ocean's public dashboard showed anomalous mining activity around the time of the incident. Mempool.space developer Mononaut observed on social media: "Oof, about 0.657 $BTC of shares earned from stolen hash, per ocean's dashboard." A suspected destination address accumulated an estimated 0.65761026 BTC in mining rewards — at current Bitcoin prices, a sum in the tens of thousands of dollars. Estimated shares, however, are not payments: available blockchain records showed no confirmed incoming transactions to the suspected address, indicating the operator had not yet collected anything from the redirected work.
CoreX Hosting, which first publicized the suspected attack, later reported that the unauthorized hashrate had declined to approximately 100 petahash per second (PH/s) — roughly 0.8 percent of the initially reported 13 EH/s figure.
Why does the incident matter for operators?
The case illustrates a threat model that does not require seizing cryptocurrency at all. An attacker who alters fleet configuration can divert revenue-generating computational power while the machines, and their owners, remain otherwise untouched. Luxor's compensation pledge addresses the immediate financial consequence; it does not answer the more consequential question of how attackers obtained sufficient control over industrial mining equipment to redirect it in the first place. The precise number of affected machines, the total computational power diverted, and the mechanics of the alleged AI-assisted compromise all await Luxor's post-mortem, which the company has committed to but not dated.
via cryptonews.net (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,525 articles