Attackers Hijack 64,000 Bitcoin Miners, Push OCEAN Hashrate Near 50 EH/s
About 64,000 Bitcoin mining machines were hijacked and roughly 13 EH/s of their computing power was redirected into the OCEAN pool starting November 14, according to Wu Blockchain. Attackers also rerouted payouts to their own Bitcoin address but mined no blocks and earned nothing. CoreX Hosting says the attack ended November 15.
- 3 sources report it: blockonomi.com, tokenpost.com, X account @Cointelegraph.
- The source published it on Nov 15, 2026 at 7:13 PM.
Nothing open. Every check passed.
Roughly 64,000 Bitcoin mining machines got hijacked, with attackers steering about 13 exahashes per second of computing power into the OCEAN mining pool. The takeover kicked off around 8 p.m. U.S. Central Time on November 14, according to Wu Blockchain. The attackers also swapped the mining payout address for a Bitcoin address under their control — and walked away with nothing.
Mining infrastructure provider CoreX Hosting raised the alarm after spotting unauthorized changes to mining pool configurations. OCEAN's mining dashboard captured the surge: hashrate briefly approached 50 EH/s, then retreated toward 40 EH/s and later sat at 41.59 EH/s. That spike was redirected power, not a matching jump in Bitcoin's overall mining capacity.
CoreX Hosting later said the attack appeared to have ended on November 15. The hijacked hashrate collapsed by more than 99%, landing at roughly 100 petahashes per second after sitting near 13 EH/s. Despite controlling all that computing muscle, the attackers never mined a Bitcoin block and collected no block rewards.
One affected operator said their entire mining farm was hijacked and named Luxor's Commander mining management software as the suspected source of the compromise. Other operators reported similar unauthorized pool-configuration changes several days before this incident, raising questions about whether the breach reached beyond the machines in the first reports. Neither the full extent of the attack nor the alleged Luxor Commander compromise has independent confirmation.
For the operators, the hit is lost hashing time that would have generated revenue through their original pools — and unlike redirected computing power, that mining time can't be clawed back. Available reports didn't quantify the financial losses or establish how many mining facilities were affected.
TopicsOCEAN · CoreX Hosting · Luxor · Luxor Commander · Wu Blockchain · Bitcoin · Bitcoin News
Written by AI from verified reporting. Not financial advice.
More stories
- Web3 & Crypto Whale move news.bitcoin.com 0 viewsBitcoin's Newest Whales Sit on Record $8B Losses and Refuse to Sell
- Web3 & Crypto Hack thedefiant.io 1 viewBitget Hack Bitcoin Moves Again, But It's No Confirmed Cash-Out
- Web3 & Crypto Hack thedefiant.io 0 viewsBitget hacker's tracked wallets dump 2,266 BTC in 11 days
- Web3 & Crypto tokenpost.com 0 viewsWintermute: Bitcoin's Bear Market Isn't Over After 12.7% Weekly Slide

