COINCRYPTO24

Luxor Commander Breach Redirects Bitcoin Miners' Hashrate to OCEAN

An attacker changed pool settings through Luxor's Commander fleet software, sending client hashrate to OCEAN. What happened, who is affected and how miners can check their fleets.

Crypto Support Desk
Crypto Support Desk

Crypto Support & Research Desk

Published Nov 16, 2026
Updated Nov 16, 2026
7 min read
Referenced Assets:General Market
Share:

Quick answer: An attacker got into Luxor's Commander fleet-management software around 02:00 UTC on 15 November 2026 and changed the pool settings on client mining rigs, sending hashrate to the OCEAN pool. Luxor says it patched the flaw within two hours, no customer data was taken, Luxor Pool and LuxOS were unaffected, and affected clients will be fully compensated.

What happened

On the evening of Saturday 14 November in the United States, about 02:00 UTC on Sunday 15 November, operators began noticing that some of their Bitcoin miners were no longer pointed at the pools they had chosen. CoreX Hosting raised the first public alarm after finding what it called unauthorized changes to pool settings on machines it hosts.

The common link was Luxor Commander, a fleet-management tool that lets mining businesses monitor and configure thousands of machines from one dashboard. One of its core features is pushing configuration changes, including pool assignments, across a whole fleet at once. According to Luxor, an attacker abused that capability to rewrite the pool settings of affected clients so that their hashrate flowed to the OCEAN mining pool, with payouts going to an address the attacker controlled.

Luxor confirmed the incident on 15 November. As reported by The Block, the company said its on-call engineers patched the vulnerability within two hours and started restoring miners to their original pool settings. Luxor said no data was leaked or exfiltrated, Commander is operating normally, and users do not need to take action.

How much hashrate moved

The size of the incident is still disputed, so it helps to separate confirmed statements from estimates:

  • Luxor's statement: "just over a dozen" customer accounts were affected, according to TokenPost.
  • CoreX's estimate: about 64,000 machines and about 13 EH/s redirected. Luxor has not confirmed this figure.
  • OCEAN's public stats: total pool hashrate briefly approached about 50 EH/s, and the address tied to the incident briefly showed close to 14 EH/s before falling toward zero as settings were restored.

For context, 13 EH/s would be a meaningful slice of the global network, which is why the incident drew attention well beyond Luxor's customers.

Did the attacker get paid?

Early reports said the attacker had received nothing because the redirected machines did not find a block. Later on-chain tracking, cited by Cointelegraph, showed that the address linked to the incident received two OCEAN payouts totalling about 0.162 BTC, roughly $10,500 at the time. That is consistent with how OCEAN pays miners: rewards are shared out in proportion to submitted work whenever the pool as a whole finds a block, so a miner does not need to find a block personally to be paid. One of the payouts, 0.081131 BTC, followed OCEAN's block 976,029.

Larger payout totals circulated on social media, but we have not been able to verify them and they are not reflected here.

Why it happened, and what Luxor says about AI

Luxor has not yet disclosed the technical entry point, whether that was stolen credentials, an API flaw or a session issue. It has promised a post-mortem. What the company has said is that this was a "sophisticated AI-enabled vector".

CEO Nick Hansen went further in public comments, warning that anyone running a substantial crypto business is now "inundated with AI-enabled attacks", and arguing that running your own GPUs with open-weight models is becoming a necessary defence. According to TFTC, Hansen said automated models are probing companies' attack surfaces around the clock. Luxor says it has bought its own bare-metal GPUs to run its own models and has paused most feature work to focus on security.

The "AI-enabled" label is Luxor's own description and has not been independently verified. It is still worth taking seriously: security firms have reported a rise in automated, AI-assisted intrusion attempts against crypto companies this year, and earlier this month we covered a separate campaign in which attackers used fake video calls to steal crypto.

Who is affected

  • Luxor Commander customers whose accounts were among the affected group. Luxor says it will compensate them for the redirected hashrate as if their machines had mined normally.
  • Hosting providers such as CoreX that manage client machines through Commander.
  • Other miners using fleet software. Commander is not the only tool of its kind. Any centralized management layer that can change pool URLs across thousands of machines is a high-value target.

People who simply hold bitcoin are not affected. No coins were stolen from wallets, no blocks were reorganized, and the Bitcoin network kept producing blocks normally. This was an attack on mining infrastructure, not on the protocol.

How miners can check their own fleets

If you run miners through Commander or any similar tool, these steps help confirm your machines are pointing where they should:

1. Compare pool URLs on every machine against your intended configuration. Check both the primary and the backup pool slots, since attackers sometimes change only the fallback.

2. Check worker names and payout addresses on your pool dashboard. A drop in your reported hashrate with no hardware fault is a warning sign.

3. Rotate credentials and API keys for your fleet software. Even if Luxor says no data was taken, rotating keys is cheap insurance.

4. Turn on multi-factor authentication or hardware security keys for every account that can change pool settings, and remove users who no longer need access.

5. Review audit logs for configuration changes made around 02:00 UTC on 15 November and afterwards.

6. Watch for Luxor's official communications about compensation and the post-mortem, and get them only through Luxor's own channels.

What it means for the market

The financial impact on Bitcoin itself is negligible. A temporary hashrate shift between pools does not change supply or block timing in any lasting way. The bigger story is about concentration risk in mining operations. As mining has industrialized, many firms rely on a few software platforms to manage large fleets. That makes operations efficient, but it also means a single compromised control plane can redirect a large share of hashrate in minutes.

The timing is also awkward for miners. Bitcoin has been under pressure this month, briefly trading near $62,000 over the weekend, as we covered in our report on weekend liquidations below $63,000. With mining margins already thin, operators can little afford lost revenue or extra security spending.

The episode echoes a familiar lesson from exchanges: after the Binance hack and phased withdrawal restoration, the weak point was operational infrastructure, not the blockchain. If you want background on how mining, exchanges and custody fit together, see our explainer on crypto market structure basics.

What to watch next

  • Luxor's post-mortem, which should explain the entry point and the timeline.
  • Compensation details for affected clients.
  • Whether OCEAN takes any action on the address tied to the incident. As of 16 November, no action had been reported.
  • Confirmation or correction of CoreX's 13 EH/s estimate.

Sources

This report draws on The Block (16 November), Cointelegraph (16 November), TokenPost (15 November) and TFTC (16 November), linked above. Payout figures come from on-chain tracking reported by those outlets. Figures attributed to CoreX are that company's estimates.

Frequently asked questions

Was the Bitcoin network hacked?

No. Bitcoin's protocol and consensus were not affected. The attacker changed pool settings inside Luxor Commander, a fleet-management tool, so some machines mined for the OCEAN pool instead of their chosen pool.

How many miners were affected by the Luxor Commander breach?

Luxor says just over a dozen customer accounts were affected. CoreX Hosting estimated about 64,000 machines and roughly 13 EH/s, but Luxor has not confirmed that figure.

Will affected miners be compensated?

Luxor says it will fully compensate affected clients for the redirected hashrate. Watch Luxor's official channels for details and never share keys, passwords or 2FA codes with anyone offering a refund.

Did the attacker earn any bitcoin?

On-chain tracking shows the address linked to the incident received two OCEAN payouts totalling about 0.162 BTC. Larger totals have been claimed online but are not verified.

What should miners using fleet software do now?

Check pool URLs and payout addresses on every machine, rotate fleet-software credentials and API keys, enforce multi-factor authentication and review audit logs for unexpected configuration changes.

This article is for general information only and is not financial, investment or security advice. Coin Crypto 24 is an independent publication and is not affiliated with Luxor, OCEAN, CoreX or any exchange or mining pool. We will never ask for your seed phrase, private keys, passwords or 2FA codes.

Regulatory & Financial Risk Disclosure

The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.

About the Author

Crypto Support Desk
Crypto Support Desk

Crypto Support & Research Desk

Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.

Source-led crypto support research