Luxor Technology disclosed on Nov. 15 that an unauthorised party had redirected bitcoin hashrate through Commander, the fleet-management software it sells to mining operators. In a statement published at 17:25 UTC, the company said the issue was patched within two hours, that it touched “just over a dozen client accounts,” and that every affected customer would be paid in full.
The diverted machines were pointed at a different pool for a limited window. Luxor said no data was leaked or exfiltrated from its systems, that Commander was operating normally afterwards, and that no action was required from users. It promised a full post-mortem.
CoreX Hosting, a hosting operator that flagged the redirect while it was underway, put the diverted total at about 13 EH/s directed to a single bitcoin address. Against the 934 EH/s of network hashrate recorded on Nov. 16, that is roughly 1.39% of all mining capacity, and about a third of the 40.35 EH/s the OCEAN pool dashboard reported the same morning. Luxor’s own statement does not repeat the hashrate figure or a machine count.
Blockchain records show the receiving address has been paid twice, for a combined 0.162 BTC. That is a small sum relative to the hashrate attributed to it, a gap Luxor has not explained, and it leaves open how much of the redirected capacity was ever credited to the address at all.
Timing is the other unresolved point. Luxor’s two-hour figure describes a vendor-side patch. Restoration was an operator-side job: at 03:57 UTC on Nov. 15, roughly two hours after the redirect began, CoreX wrote that the attack was still ongoing with the address sitting at 13 EH/s, adding that it was changing miners back as fast as it could. A patched control plane and a fully restored fleet are not the same event.
The mechanism is mundane and that is what makes it notable. Mining fleets are now run through software dashboards sold on service contracts, and the revenue those fleets produce settles in coinbase transactions that no bank can freeze or reverse. Whoever controls the dashboard controls the payout address, and changing a pool setting requires no data exfiltration at all.
Luxor’s compensation principle, paying affected clients as if the machines had mined normally, puts the loss on the vendor rather than the operator. Whether the post-mortem explains the hashrate discrepancy, the shortfall between 13 EH/s and 0.162 BTC, and how an attacker obtained the access needed to re-point other companies’ machines will determine how much of the incident was a software failure and how much was an access-control one.