Skip to main content

Luxor says attackers redirected client hashrate through Commander

16 NOVEMBER 2026·2 MIN READ·3 SOURCES

Luxor said attackers exploited its Commander fleet-management software to redirect client hashrate to another mining pool, affecting more than a dozen client accounts. The company’s CEO called the incident AI-enabled, but did not explain how AI was used.

Luxor says attackers redirected client hashrate through Commander

Key takeaways · 4

  • 01

    The confirmed impact was more than a dozen client accounts; Luxor did not confirm reports of about 64,000 machines or 13 exahashes per second being redirected.

  • 02

    Luxor said the vulnerability was patched within two hours, and engineers began restoring affected machines to their original pool settings.

  • 03

    Luxor said no data was leaked and that users did not need to take further action while Commander operated normally.

  • 04

    The CEO described a “sophisticated AI-enabled vector,” but Luxor did not explain how AI was used in the incident.

What Luxor confirmed

Luxor said attackers exploited Commander, its fleet-management software, to redirect client hashrate to another mining pool.[1] The company said it detected the unauthorized redirects on Saturday and that more than a dozen client accounts were affected.[1] Luxor said the issue was isolated to Commander and did not affect its other services, including Luxor Pool and LuxOS.[2] Those statements establish the confirmed scope, while larger figures circulating in early accounts remain unconfirmed by Luxor.[2]

Patch, restoration and compensation

After the patch, engineers began restoring affected machines to their original pool settings.[1] Luxor said no data was leaked or exfiltrated and that Commander was operating normally, with users not needing to take further action.[1] The company also said it plans to fully compensate affected clients for the redirected hashrate.[1] These are Luxor’s statements about its response and commitments; the evidence does not specify a compensation schedule.[1]

What the AI description tells us

CEO Nick Hansen described the incident as involving a “sophisticated AI-enabled vector,” but did not explain how AI was used.[3] Hansen also said Luxor had put most new feature development on hold while responding to weeks of AI-assisted attacks.[3] He said engineers were rotating access keys, updating systems and addressing newly disclosed vulnerabilities.[3] Separately, Cointelegraph reported that Luxor had acquired GPUs to run unrestricted open-weight AI models to improve its security posture.[2] Luxor pledged to publish a post-mortem, which could provide further detail.[2]

Pool payments and uncertain scale

CoinDesk reported that the redirected machines were sent to OCEAN, a pool where miners combine computing power and share bitcoin rewards with subscribers.[3] OCEAN’s payout rules keep previously submitted work eligible for a share of subsequent block rewards for a rolling period.[3] An address initially flagged by mining host CoreX Hosting received three block-reward payments totaling about 0.243 BTC, worth roughly $15,700; CoinDesk reported that none had been spent as of Monday morning.[3] Cointelegraph reported that estimates of about 64,000 machines and 13 exahashes per second being redirected were not confirmed by Luxor.[2]

For teams that rely on mining-management software, the key distinction is between the confirmed Commander incident and the larger, unconfirmed estimates. The AI description is also a reminder to distinguish a company’s characterization of an attack from a disclosed explanation of how it worked.

Why it matters
For teams

AI training for your team

kju.ai is built for teams: daily sessions, team analytics, and rollout support for your organization.

How this developed

  1. 16 November 2026

    Luxor says attackers redirected client hashrate through Commander

Sources

AI fluency, one session a day, built for your work.