Luxor: an "AI-enabled" attack redirected up to 13 EH/s of bitcoin mining power

On the evening of 14 November 2026, attackers used Luxor's Commander fleet software to point miners at another pool and collect the rewards. Up to about 1.4% of Bitcoin's hashrate was diverted for a few hours. What happened, what was and was not at risk, and what it says about management tools.

By SeedCrypt Editorial4 min read

Key facts

  • When: the evening of Saturday 14 November 2026, Pacific time. The hosting company CoreX said the attack was contained by 01:40 ET on 15 November.
  • How: attackers changed the pool settings of mining machines through Luxor Commander, a fleet management platform, and redirected their hashrate to the OCEAN pool under a payout address they controlled.
  • Scale: up to about 13 EH/s, roughly 1.4% of Bitcoin's hashrate, according to CoreX. Luxor says "just over a dozen" client accounts were affected.
  • Attacker's take: between about 0.162 and 0.243 BTC in pool payouts.
  • Not affected: the Bitcoin network, user wallets, Luxor's mining pool and its LuxOS firmware. Luxor says no data left its systems and it will pay affected clients in full.

What happened

Luxor sells software and services to bitcoin miners. Commander, launched in April 2026, lets mining companies manage their fleets of machines from one place: monitoring, power settings and which pool each machine sends its work to.

On the evening of 14 November, attackers used Commander to change the pool settings of machines belonging to Luxor clients. The machines kept mining, but for the OCEAN pool, with rewards going to an address controlled by the attackers. CoreX Hosting, a company that hosts mining machines, raised the alarm after seeing thousands of machines connect to OCEAN under a single unknown payout address. At its peak, CoreX estimated about 13 EH/s had been redirected. One report put the number of machines at about 64,000; Luxor itself spoke of "just over a dozen" client accounts and did not give a machine count.

Luxor says its engineers patched the flaw within about two hours of detecting it and put the machines back on their original pools. By 01:40 ET on 15 November, CoreX said the redirected hashrate had fallen from 13 EH/s to about 100 PH/s.

How much was stolen

The attackers did not find any blocks themselves during the window. But on OCEAN, miners are paid for the valid work they submit when the pool finds blocks, so the address controlled by the attackers still received two to three payouts, between about 0.162 and 0.243 BTC depending on the report, roughly $10,500 to $15,700.

For the miners, the real loss is the revenue their machines did not earn for them during those hours. Luxor has promised to pay every affected client in full, "as if it had mined normally".

The "AI-enabled" claim

Luxor's chief executive, Nick Hansen, described the attack as using a "sophisticated AI-enabled vector" and apologised to clients: "You trust us with your fleet, and we need to be better." Luxor has not explained what the vulnerability was, how the attackers got in, or what role AI played, and has promised a full post-mortem. Until it is published, the AI part is the company's description, not something that can be checked. Luxor has said it is pausing most new features to focus on security, and is deploying AI models on its own hardware to test its systems.

What was not at risk

This was an attack on a management tool, not on Bitcoin. The protocol was not affected, no coins were taken from user wallets, and 1.4% of the hashrate for a few hours is far from the majority an attacker would need to rewrite transactions. The bitcoin price did not react.

What to take away

  • A management console is a master key. One platform with the right to change every machine's settings became the single place an attacker needed to reach, whatever the security of each machine.
  • The payout address is the target. Whether it is a mining pool setting or a crypto address on a web page, attackers increasingly go for the one field that decides where the money goes. Alerting on any change to it is a cheap defence.
  • Detection came from outside. It was a hosting provider watching its own network, not the platform, that first noticed thousands of machines pointing to an unknown address.
  • For individual holders, the lesson is the same as always: the closer a system is to your keys, the fewer third parties should be able to change it. A recovery phrase that no platform holds is one no platform can lose.

This article is based on Luxor's statements and public reports available on 17 November 2026. Luxor had not yet published its post-mortem, and the figures for hashrate and machines come from third parties.

Sources

SeedCrypt · Our product

Your seed phrase, encrypted offline

Download free, decrypt free forever, and encrypt from 10 €. No sign-up, no subscription, no internet connection needed.

  • Works offline
  • No account
  • 14-day money-back guarantee
  • Card or crypto