What happens to a miner’s earnings when fleet-management settings point its machines to the wrong pool? In an incident reported on November 17, 2026, Luxor Technology said an unauthorized change in its Commander software had redirected hashrate from just over a dozen client accounts to a different mining pool for a limited period.
Luxor said its internal monitoring detected the change. The company patched Commander within two hours and began restoring the affected machines’ original settings. It said it would pay every affected client in full for the redirected hashrate, as if their machines had mined normally. That is a commitment from Luxor, not a reported calculation of each client’s loss.
CEO Nick Hansen said the compromise began around 6 p.m. Pacific time on the preceding Saturday through what he called a “sophisticated AI-enabled vector.” He did not explain how it worked, so the role of AI in the breach remains his characterization rather than a disclosed technical finding.
According to Luxor, the issue was confined to Commander: no data was leaked or taken from its systems, and neither Luxor Pool nor LuxOS was affected. Hansen said the company had also paused most new-feature work to strengthen its infrastructure, including rotating keys, updating kernels and pinning dependencies. Luxor said it planned to publish a full post-mortem.


