Luxor Technology has confirmed that attackers used its Commander platform to redirect bitcoin mining hashrate from a subset of customer accounts, settling earlier speculation over whether a mining hijack had actually occurred. The company said the incident was identified through internal monitoring, contained within two hours, and did not result in stolen information.
Luxor also said it will fully compensate affected customers for the mining output diverted during the breach. Chief Executive Nick Hansen later described the event as a sophisticated AI-enabled intrusion, though the company has not yet released the technical details behind that claim.
What Luxor says happened
In its statement, Luxor said engineers detected unauthorized changes to mining pool settings inside Commander, its mining management platform. The company said those changes caused mining machines tied to just over a dozen customer accounts to be redirected temporarily to another pool.
According to Luxor, the engineering team responded immediately after detecting the unauthorized redirect. Commander was patched within two hours, and the affected equipment began to be restored to its original configurations. Luxor said no customer information was stolen from its systems during the incident.
The company added that every affected customer will be reimbursed as if the redirected hashrate had continued mining normally. That commitment covers the computational power diverted during the disruption rather than any direct theft of bitcoin from user wallets.
Earlier reports pointed to a much larger event
Before Luxor publicly acknowledged the breach, reports had circulated claiming that about 64,000 mining machines, or roughly 13 exahash per second of hashrate, had been redirected to the Ocean mining pool. Those figures remain unverified.
Luxor's disclosure confirms unauthorized redirection occurred, but it does not confirm the reported machine count or the total amount of computational power affected. A compromise involving just over a dozen customer accounts does not by itself establish how many individual machines were involved.
Public data from Ocean showed unusual mining activity around the time of the incident. A suspected destination address was estimated to have accumulated about 0.6576 BTC in mining rewards, but that estimate did not prove the operator had actually been paid. Blockchain records cited in the report showed no confirmed incoming transactions to the address, suggesting the redirected mining activity may not yet have yielded collected bitcoin.
CEO cites an AI-enabled attack
Hansen said the incident began at around 6:00 p.m. PDT on Saturday, when a subset of Commander customers was compromised through what he called a sophisticated AI-enabled vector. He apologized to customers and said affected users would receive more information by email.
That description adds a possible explanation for the intrusion, but Luxor has not yet published a technical breakdown showing how attackers gained access or how the mining configurations were changed. For now, the AI-related characterization remains the company's account rather than a documented public finding.
Luxor said engineers both identified and patched the issue before restoring machines. The company has not yet provided a machine count, a total hashrate figure, or a detailed explanation of the attack path.
What remains unresolved
Luxor's confirmation answers the core question of whether an unauthorized hashrate redirect took place: it did. Even so, several important details remain unsettled, including the precise number of mining machines involved, the amount of hashrate diverted, and the exact technical mechanics of the breach.
The next confirmed step is a fuller post-mortem from Luxor. That report is expected to clarify how the attackers obtained enough control over fleet settings to reroute industrial mining equipment and to provide a more complete accounting of the incident's scope.
Source: news.bitcoin.com