Bitcoin Miners Hijacked via Luxor Commander: What Is Confirmed and What Is Not
Attackers reportedly redirected Bitcoin miners to the OCEAN pool through Luxor’s Commander platform. What Luxor confirmed, what is still unverified, and what miners and hosting clients should do.
A hashrate hijack is an attack in which someone changes the mining pool settings of other people's machines, so those machines work for the attacker's payout address instead of their owner's.
Based on public reports from 15–16 November 2026. Several details below are still unverified, and we mark them clearly. We will update this article when Luxor publishes its post-mortem.
What happened
On Saturday 14 November, at around 6 p.m. Pacific time, an unauthorized party changed mining pool configurations through Luxor's Commander platform. Commander is software that lets operators manage the settings of many mining machines at once. According to Luxor's CEO, the company's monitoring flagged the redirect the same night, and Luxor published a public statement on Sunday 15 November.
Affected machines were pointed at a different pool, OCEAN, and worked for an address controlled by the attacker.
What Luxor has confirmed
According to its own statement, as reported by Bitcoin.com News:
- Pool configurations were changed without authorization through Commander.
- "Just over a dozen" customer accounts were affected.
- Luxor's own mining pool and its LuxOS firmware were not affected.
- No data was stolen or exfiltrated.
- Commander was patched within about two hours, and affected machines are being restored to their original settings. Luxor says the restoration was slower than the patch.
- Luxor says it will fully compensate affected customers for the diverted hashrate and will publish a post-mortem.
What is not confirmed
- The size of the attack. Media reports cite about 64,000 machines and 13 EH/s. Luxor did not give a machine count, only the number of accounts, and these figures remain independently unverified. CoreX Hosting later said the diverted hashrate had fallen to about 100 PH/s.
- The "AI-enabled" claim. Luxor's CEO described the attack as a "sophisticated AI-enabled vector." The company has not published technical findings on how the attackers got in, so this claim cannot be checked yet.
- How the attacker got in. Nobody has publicly explained whether this was stolen credentials, a software flaw or something else.
How the attacker was paid
OCEAN does not require an account. A miner's payout address works as the login, and the pool pays out through the coinbase transaction of the blocks it finds. This design is why a hijack like this can pay off for the attacker quickly. It was not a flaw that someone exploited, and OCEAN has published no statement about the incident as of this writing.
Blockchain records show two coinbase payments to the address reportedly linked to the redirect, in blocks 975,995 and 976,029. They total 0.16202083 BTC, roughly $10,500 at the time of reporting, and neither output had been spent. OCEAN's dashboard showed a larger estimated pending amount, about 0.66 BTC, but an estimate on a dashboard is not money received.
This has happened before
In 2014, attackers used BGP hijacking to reroute the network traffic of miners to their own pool. Researchers estimated the haul at around $83,000, mostly in altcoins. The method was different (the network, not the management software), but the goal was the same: make other people's machines work for you without touching the miners themselves. The lesson repeats every few years: whoever controls the settings of a mining fleet controls its income.
What to do if you mine or host machines
- Check your pool settings now. Log in to your dashboard and confirm that the pool URL and payout address on every machine are the ones you set.
- Watch your hashrate on your own pool. A sudden drop that you did not cause is the first sign of a redirect.
- Turn on two-factor authentication everywhere you can, and use unique passwords for management software. See why crypto accounts need two-factor authentication.
- If you use a hosting provider or fleet software, ask questions. Who can change your pool settings? Is there an audit log? Are changes confirmed by a second factor? Our list of questions to ask before you pay for hosted mining covers more.
- Keep records. If you were affected, save screenshots and logs of your hashrate for the compensation process.
What does this mean for people who do not mine?
For most people, nothing changes directly. Bitcoin itself was not attacked, and the redirected hashrate did not give anyone control over the network. For people who buy mining contracts, though, the lesson is practical: a provider's security is part of what you pay for. See how to recognize a fake mining contract and the traps around mining hardware pre-orders. If an exchange or service you use is ever breached, here is what to do.
What to watch next
- Luxor's post-mortem and any explanation of the entry point.
- Whether OCEAN comments, and whether the attacker's coins move.
- Whether Luxor publishes the real number of affected machines.
If you want to check a crypto address or token before you interact with it, you can run a free scan on ScamSonnar.
This article is for information only and is not financial advice. Verify the facts yourself using the sources below.
Sources
- Luxor Confirms Bitcoin Mining Hack and Reveals AI-Enabled Attack – Bitcoin.com News
- Luxor Commander Hijack: 0.162 BTC In Payouts – Blockchain Reporter
- 64,000 Bitcoin Mining Machines Reportedly Hijacked as 13 EH/s Redirected to OCEAN Pool – FinanceFeeds
- Attackers hijack about 64,000 Bitcoin miners and point 13 EH/s at OCEAN – Crypto Briefing via TradingView
- Bitcoin mining heist via BGP hijack, 2014 – The Register