Luxor: Attackers Took Over a Dozen Clients' Bitcoin Miners and Sent the Power to Another Pool
Attackers used Luxor's Commander software to redirect about 13 EH/s of mining power on 14 November. One address earned about 0.162 BTC. Luxor says a dozen accounts were hit.

Key numbers
~13 EH/s
Mining power diverted (reported)
~64,000
Machines (CoreX / GalaxyMind estimate)
Just over 12
Client accounts (Luxor)
~0.162 BTC
Earned by attacker address
On the evening of Saturday 14 November 2026, someone used Luxor's Commander software to change the settings of bitcoin mining machines that belonged to its customers. The machines kept working, but their output went to a different mining pool, one the owners had not chosen. Luxor, a US mining-services company, confirmed the incident on 15 November. It says just over a dozen client accounts were affected. Outside estimates reported by The Block, TFTC and CryptoSlate put the total at about 64,000 machines and 13 EH/s. Luxor has not confirmed the machine count.
Mining, hashrate and pools in plain words
Bitcoin mining is how new bitcoin is created and how payments are checked. Special computers, called miners, guess numbers all day. Whoever finds the right number first gets to add the next batch of payments to the public ledger and earns a reward in bitcoin. Hashrate is the number of guesses a machine or fleet makes each second. One EH/s, an exahash per second, is a billion billion guesses per second, and CoinSpect said 13 EH/s is about 1.5% of the whole bitcoin network.
Guessing alone is a lottery, so most miners join a mining pool. A pool adds up everyone's guesses, shares the prizes in proportion to the work each member did, and sends each member a cut. Think of it as a lottery syndicate. Commander is Luxor's fleet-management software. A mining firm with thousands of machines uses it to set, in one place, which pool all of them work for.
A fair comparison is borrowing someone's factory for a night. The machines, the electricity and the bills belong to the owner. The person who grabs the controls only has to change the delivery address on the finished goods. That is what the attackers did.
What Luxor says
Luxor's statement, posted on X on 15 November, said: "Impact: just over a dozen client accounts." It said the company's monitoring caught an unauthorized redirect of hashrate through Commander, that "within 2 hours Commander was patched and we started restoring affected machines", and that "every affected client will be paid in full for the redirected hashrate, as if it had mined normally." It also said no data was leaked or taken from its systems, and that its mining pool and its machine firmware, LuxOS, were not affected.
Chief executive Nick Hansen put the total at about 13 EH/s in comments to The Block, saying that was "~$20,000/hr, so time was of the essence." He also said the incident "really wasn't a major blow" in bitcoin terms. He wrote that the attack began around 6 p.m. Pacific on 14 November.
The numbers that do not match
The 64,000-machine figure came from CoreX Hosting, a mining-site operator that raised the alarm, and from the analyst group GalaxyMind. CryptoSlate and TFTC both say Luxor has not confirmed it. The gap with "just over a dozen" is not necessarily a contradiction. A few large clients can own thousands of machines each. But no source has published a list of the accounts or the machine counts per account.
OCEAN, the pool that received the power, showed on its public dashboard a rise to nearly 50 EH/s, according to reports, before it fell back toward 40 EH/s. CoreX declared the incident over after the diverted power fell to about 100 PH/s, roughly 99% lower.
Did the attackers get paid?
First reports said the attackers earned nothing, because no block was found with the borrowed power. That was wrong. Pools pay for recent work, not only for the block that happens to be found while a miner is connected. CoreX identified one bitcoin address that received two payouts from OCEAN. According to Blockchain Reporter, citing mempool.space and OCEAN's dashboard, block 975,995 on 15 November paid 0.08088977 BTC and block 976,029 paid 0.08113106 BTC. That totals 0.16202083 BTC, about $10,500 at the time. CryptoSlate reported three payments adding up to 0.24308905 BTC by 16 November. The two reports have not been reconciled. As of 16 November the coins had not been moved.
Neither report shows who controls the address. OCEAN did not take the money from anyone. It paid out shares of work it was sent, and Luxor, CoreX and the outlets reviewed do not accuse the pool of wrongdoing. No reply from OCEAN appeared in any source reviewed.
The AI claim and the open question
Hansen called the method "a sophisticated AI-enabled vector" and said "abliterated models are running 24/7 against your entire surface". Abliterated models are AI systems with their safety limits stripped out. He said Luxor had bought its own GPU computers to run such models for defensive testing. Luxor has not said how the attackers got in, and no source verifies that AI was used. Commentators note the cause could be as ordinary as stolen logins to a few accounts. Luxor has promised a post-mortem, which had not appeared in any source found by 18 November.
The aftermath
Luxor says every affected client will be paid in full for the redirected hashrate, but it has published no terms. It says Commander runs normally and users need take no action. The cause, the real number of machines and the identity of the address holder are unknown. The Block reported that Luxor raised $16 million the month before, led by CMT Digital.
What this teaches
- Software that controls a whole fleet from one screen is a single point of failure.
- Mining pools pay for recent work, so a redirect can earn money even after it stops.
- A claim of AI-enabled attack needs the method published before it can be judged.
- Compare the company's account count with outside machine estimates before trusting either.