Luxor said on Sunday that attackers carried out “an unauthorized redirect of hashrate through Commander,” its fleet-management software, and that the incident affected “just over a dozen client accounts.” The company said it patched Commander within two hours of an internal alert and that every affected client will be paid in full for the redirected hashrate. The confirmation comes after AltcoinReporter’s Sunday report on mining machines being pointed at the OCEAN pool, when Luxor had not yet commented.
What Luxor has confirmed
“Last night our internal monitoring alerted us to an unauthorized redirect of hashrate through Commander,” Luxor said. “Our on-call engineering team jumped on it right away.”
The company described the impact in these terms: “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.” It did not give a machine count, a hashrate total or a name for the destination pool.
On the response, Luxor said: “within 2 hours Commander was patched and we started restoring affected machines to their original pool settings.” That two-hour claim is measured from the moment monitoring alerted the team, and it covers the patch, not a statement that every machine was back on its original pool in that window.
On compensation, it said: “every affected client will be paid in full for the redirected hashrate, as if it had mined normally.” It added that Commander “is operating normally and no action is needed from users,” and that a “full post-mortem” would follow, with no date attached.
In a follow-up a few minutes later, Luxor said the issue “was isolated to the Commander tool” and that “None of Luxor’s other services (including Luxor Pool and LuxOS) were affected.”
What the CEO added
Luxor CEO Nick Hansen, posting shortly before the company statement, said “a subset of Commander customers were compromised, through a sophisticated AI-enabled vector.” The “AI-enabled” description is Hansen’s. It does not appear in Luxor’s company statement, and no forensic report has been published to support it.
“We were able to identify and patch quickly so that it didn’t continue, then the hard work of reverting started,” Hansen said. He said affected clients “will receive an email today with more details,” and he apologized: “You trust us with your fleet, and we need to be better.” Early on Monday, in a reply, he said “The email should be out.” That is not confirmation that every client has received payment, or even the email.
Later on Sunday, Hansen wrote that “anyone running any sort of substantial business, especially in crypto, is inundated with AI-enabled attacks,” and he described an “AI-powered dark forest.” He said Luxor has acquired its own bare-metal GPUs to test models against its systems and has put most new feature work on hold to harden infrastructure. Luxor quoted that post. Those comments describe a broader security posture. They are not a technical finding on how this intrusion happened.
How this sits with Sunday’s report
The OCEAN destination, the 13 EH/s peak, the estimate of around 64,000 machines and the figure of about 0.66 BTC in unpaid shares all come from that Sunday article and the sources it cited. It reported CoreX Hosting’s warning that machines were being pointed at OCEAN and that the attacker’s pool address was at one point “still sitting at 13EH,” and it noted that Bitcoin News and TokenPost estimated around 64,000 machines. It also cited about 0.66 BTC of unpaid shares on OCEAN’s dashboard, a projection under the pool’s TIDES payout window, not confirmed profit. Luxor has not confirmed any of those figures. Its statement says only that machines from just over a dozen client accounts were pointed to a different pool for a limited window, and it has not named that pool.
After that Sunday article was published, the Bitcoin address CoreX named, bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr, received two payments in OCEAN block coinbases: 0.08088977 BTC in block 975,995 and 0.08113106 BTC in block 976,029, totaling 0.16202083 BTC, or about 0.162 BTC. Cointelegraph also reported two OCEAN payouts to that address totaling about 0.162 BTC. Those amounts are later payments from the share window, not a final profit figure, and they are not the same as the 0.66 BTC projection. More OCEAN blocks may still pay. The outputs had not been spent when this article was written. Luxor has not confirmed any attacker proceeds.
What is still open
Luxor has not published the promised post-mortem, so the path into Commander, the length of the redirect, and how compensation will be calculated remain undisclosed. It has also not said whether every redirected machine has been restored. This is a vendor-software incident, not a failure of the Bitcoin protocol or of Luxor Pool or LuxOS, according to the company.
FAQ
How many Luxor clients were affected? Luxor said the incident affected “just over a dozen client accounts.” It has not published a machine count or a hashrate total, and it has not confirmed unofficial estimates circulating from Sunday.
Has Luxor already paid the affected clients? No payment has been confirmed. Luxor said every affected client will be paid in full for the redirected hashrate. Hansen said an email with details should have gone out, which is not the same as funds received.
Were Luxor Pool or LuxOS breached? Luxor said the issue was isolated to Commander and that its other services, including Luxor Pool and LuxOS, were not affected. It also said no data was leaked or exfiltrated from its systems.
Disclaimer: This article is for informational purposes only and does not constitute financial advice.


















