MediumBreach / campaignMonitoring

Luxor says AI-enabled attack redirected client hashrate in Commander

The Cyber Express reports Luxor says an attacker redirected client hashrate via its Commander software; Luxor says no user action is needed.

Published
Exploitation
Yes, according to Luxor as reported by The Cyber Express; no independent verification

What happened

According to The Cyber Express, Luxor Technology, a Bitcoin mining infrastructure firm, confirmed a breach on November 15, 2026. The outlet reports that an intruder hijacked Commander, Luxor’s platform for monitoring and configuring large mining fleets, and sent customers’ hashrate to another pool. The Cyber Express says the machines kept running but the rewards went elsewhere.

Per the same report, the redirects began around 6:00 PM PDT on Saturday, November 14. Attackers redirected hashrate from over a dozen client accounts to OCEAN, a separate mining pool. Luxor said in posts on X, as relayed by The Cyber Express, that its monitoring caught the unauthorized redirects. Its on-call engineers patched the flaw within two hours and restored machines to their original pool settings.

The Cyber Express reports the attacker’s payout address received about 0.162 BTC, and that diverted hashrate peaked at an estimated 13 EH/s, roughly 1.4% of the network’s total at the time.

CEO Nick Hansen attributed the attack to a sophisticated, AI-enabled attack vector, according to The Cyber Express. This is Luxor’s characterisation. The outlet does not describe any independent verification of it.

Luxor also said, per The Cyber Express:

  • No data was leaked or exfiltrated.
  • The issue was isolated to Commander. Luxor Pool and the LuxOS firmware were unaffected.
  • Commander is operating normally.
  • Affected clients will be fully compensated and credited as if their hashrate had performed normally.
  • A post-mortem will be published.

Not confirmed in the source: the specific flaw or entry point, the exact number of affected accounts, who the attacker is, and whether the AI-enabled claim holds. No CVE is cited.

Am I affected?

According to The Cyber Express, the incident was limited to Commander, with over a dozen client accounts redirected. If you use Commander, you may have been among the affected clients, which Luxor says will be compensated and credited. The source does not say how affected clients are identified or notified. If you use only Luxor Pool or the LuxOS firmware, Luxor says those were unaffected. Luxor says users do not need to take any action.

What to do now

  1. Read Luxor’s own statements on X and any customer communication, since the account here comes from a single outlet relaying them.
  2. If you use Commander, review your pool configuration and payout address history for the weekend of November 14 and 15. This is our suggested check, not a step Luxor requires.
  3. If you saw reduced rewards in that window, contact Luxor about the compensation it says it will provide.
  4. Watch for the post-mortem Luxor says it will publish. It should clarify the flaw and entry point, which are not confirmed today.

Sources