Hackers Redirected 64,000 Bitcoin Mining Rigs to OCEAN Pool
Key Takeaways
- •Attackers compromised just over a dozen customer accounts on Luxor Commander and rerouted approximately 64,000 mining machines to the OCEAN pool without the owners' knowledge.
- •The hijacked hashrate, estimated at 13 EH/s, briefly pushed OCEAN's total capacity to nearly 50 EH/s before the vulnerability was patched within about two hours.
- •Because block discovery is probabilistic and the redirection window was short, no Bitcoin block was mined and the attacker's address received only about 0.162 BTC, worth roughly $10,500.
- •Luxor stated that no customer data was stolen, pledged to pay every affected client in full for the redirected hashrate, and plans to publish a complete post-mortem report.
- •CEO Nick Hansen warned that AI systems may now continuously scan exposed software for weaknesses, prompting Luxor to acquire GPUs to run open-weight AI models defensively.

Hackers took control of roughly 64,000 Bitcoin mining machines on November 14, 2026, and redirected their computing power to the OCEAN mining pool without the owners’ knowledge. Luxor Technology confirmed that its Commander fleet-management software had been exploited, but the attackers obtained little from the operation: no Bitcoin blocks were mined with the unauthorized hashrate.
How the mining rigs were redirected
Bitcoin mining machines contribute computing power, or hashrate, to mining pools. A pool combines the hashrate of participating machines to search for a valid solution to Bitcoin’s cryptographic puzzle. When the pool discovers a block, it receives the block reward and distributes proceeds among contributors according to their share of the work.
In this incident, the attacker gained access to Luxor Commander, a platform that allows mining operators to configure and manage thousands of machines simultaneously. Luxor CEO Nick Hansen said just over a dozen customer accounts were compromised. The attacker then silently changed the pool destination for approximately 64,000 machines, sending their computing power to OCEAN, a Bitcoin mining pool focused in part on decentralization. Because platforms like Commander centralize the pool-routing settings for entire fleets, a single compromised account can shift the earnings destination of tens of thousands of machines at once — no physical access to the hardware required.
CoreX Hosting, a mining-facility operator, was the first to raise the alarm after detecting unauthorized pool-configuration changes on its machines. Luxor identified the breach at around 6 p.m. PDT on November 14 and said it had been carried out through what Hansen described as “a sophisticated AI-enabled vector.” The company patched the Commander vulnerability within two hours of detecting the incident. CoreX Hosting confirmed that the issue had been resolved on November 15.
The redirected hashrate was estimated at 13 EH/s, or exahashes per second. That represents approximately 13 million trillion hashing operations per second. OCEAN’s total hashrate temporarily climbed to nearly 50 EH/s, producing a sharp and anomalous increase.
The incident is part of a broader pattern in which attackers use automated tools to probe software platforms at scale. Similar AI-assisted attacks have previously targeted Bitcoin users, with attackers seeking weaknesses in account-security systems and configuration interfaces. For mining operations, the episode shows that the software used to route hashrate can itself become the target, since whoever controls pool configuration controls where the resulting rewards are paid.
Why no Bitcoin block was mined
Despite controlling about 13 EH/s of mining power, the attackers did not mine a single Bitcoin block during the incident. Bitcoin block discovery is probabilistic, meaning that even a pool with substantial hashrate is not guaranteed to find a block during any particular period.
The unauthorized redirection lasted only about two hours, ending when Luxor patched Commander. That brief window apparently was not long enough for OCEAN to solve a block using the stolen hashrate — a reminder that hijacked hashrate produces revenue only if a block is actually found before the hijack is cut off.
The Bitcoin address associated with the attacker received two small payouts from OCEAN totaling approximately 0.162 BTC, worth about $10,500 at the time. The payments were likely partial mining credits accumulated before the redirection was stopped, representing a small return relative to the scale of the operation.
Blockchain analyst mononaut separately cited an unconfirmed figure of approximately 0.657 BTC through OCEAN’s dashboard. That amount had not been independently verified on-chain.
Luxor’s response and AI warning
Luxor said that no customer data was stolen and that the incident was limited to Commander’s pool-routing feature. The company pledged to compensate affected customers fully for the redirected hashrate. “Every affected client will be paid in full for the redirected hashrate, as if it had mined normally,” Hansen said in a statement reported by Bitcoin.com.
Hansen also warned that the attack reflected a change in the way vulnerabilities may be discovered. Instead of relying solely on people to search manually for weaknesses, he said automated artificial-intelligence systems may continuously examine exposed software and infrastructure.
“Abliterated models are running 24/7 against your entire surface, looking for a little crack. It’s your only defense in this new AI-powered dark forest.” — Nick Hansen, Luxor Technology CEO, via Cointelegraph
The “Dark Forest” is a term used in computer security and science fiction to describe an environment in which autonomous threats continually search for vulnerabilities. Hansen said Luxor had acquired its own GPUs to run open-weight AI models defensively. He also apologized to customers, saying: “I apologize. You trust us with your fleet, and we need to be better.”
The attack was not unique to mining software. Hackers have also used public blockchains to keep malware infrastructure online, illustrating the methods attackers can use when targeting cryptocurrency systems. The incident highlights the security risks faced by operators that manage Bitcoin mining hardware through third-party platforms, including the need to review account settings and use multi-factor authentication where available.
OCEAN, the pool that received the redirected hashrate, had not publicly commented on the incident as of the report. Luxor said it would publish a full post-mortem report, but that report had not been released at the time of writing. For mining operators following the case, the items to watch are whether the pledged compensation is delivered in full and what the post-mortem says about how the breach was carried out.
The original report was published by CoinLineup.
This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital-asset markets carry significant risk. Readers should conduct their own research before making decisions.