1. Home
  2. Mining & Staking
  3. Hackers Hijack 64,000 Bitcoin Miners in Massive OCEAN Pool Redirect

Hackers Hijack 64,000 Bitcoin Miners in Massive OCEAN Pool Redirect

AI persona · Mining & staking · Michael Nguyen · All content is researched and edited by AI and verified by Super Intelligence. Drafted November 15, 2026. How it works · Report an error

Hackers hijacked approximately 64,000 Bitcoin mining machines on November 15, 2026, diverting roughly 13 exahashes per second of computing power to the OCEAN mining pool in a sudden security breach that tested industrial mining operations while Bitcoin traded near 65,518 USD.

By Michael Nguyen | November 15, 2026

For everyday Bitcoin holders, the headline sounds alarming, yet the Bitcoin blockchain itself never missed a beat. Attackers failed to find a single block during the brief hijack window, meaning they walked away with zero block rewards, while affected mining companies absorbed the lost income on their own balance sheets. Still, with Bitcoin trading at 65,518 USD and profit margins already razor-thin, the breach exposes how a single remote software layer can turn thousands of expensive machines into unpaid workers overnight.

Table of Contents

The Hardware/Software Landscape

Modern Bitcoin mining runs on specialized computers called ASIC miners, which are single-purpose machines built solely to solve cryptographic puzzles and earn Bitcoin rewards. Large facilities run tens of thousands of these rigs side by side, and operators rely on remote dashboards to reboot machines, update software, and switch mining pools—which act like shared lottery syndicates where miners combine computing power to earn steadier payouts.

According to reports from TokenPost and KuCoin, U.S.-based hosting firm CoreX Hosting raised the first public alarm after spotting machines switching pools without permission. Affected operators pointed suspicion toward Luxor’s Commander, a cloud-based fleet management platform built by Luxor Technology that uses a local software agent to control hardware from major brands like Bitmain, MicroBT, and Canaan.

  • 64,000 mining rigs — The estimated number of Bitcoin machines redirected without owner authorization during the breach.
  • 13 exahashes per second — Total computing power briefly routed to attacker-controlled payout addresses on the OCEAN mining pool.
  • Near 50 EH/s peak — OCEAN’s public dashboard briefly surged toward 50 exahashes per second before falling back near 40 exahashes per second.
  • Zero blocks stolen — Attackers failed to win a block reward before operators cut off the unauthorized redirect.

Whether the intrusion stemmed from a direct flaw in Commander or compromised operator login credentials remains under investigation, with formal root-cause confirmation from Luxor still pending. Shortly after alerts spread across the industry, CoreX Hosting reported that the hijacked power collapsed back down to roughly 100 petahashes per second, restoring normal pool routing for most sites.

Hashrate & Difficulty

To understand why the Bitcoin network stayed safe, look at the raw scale of global computing power. Hashrate measures how many workers are mining on the network at any moment, expressed in exahashes per second. Leading into this weekend, data reported by The Defiant and CryptoBriefing showed the seven-day average network hashrate sitting between 930 and 960 exahashes per second, so the 13 exahashes per second hijacked by attackers represented only a small slice of global capacity.

The breach also landed one day after a major relief valve opened for legitimate operators. On November 14, 2026, at block 975,744, Bitcoin’s automated mining difficulty—the built-in dial that adjusts how hard it is to find a new block—dropped by 9.13 percent, sliding from 148.36 trillion down to 134.82 trillion.

That cut marked the steepest downward adjustment since June 2026, according to TradingView and The Defiant. It kicked in because slower block times, averaging roughly 11 minutes over the prior two-week cycle instead of the usual 10-minute target, showed that struggling miners had already been unplugging unprofitable machines.

Profitability Metrics

Mining economics leave almost no room for unscheduled downtime right now. Industry data tracked by KuCoin and CryptoSlate shows hashprice—the expected daily gross revenue earned by one petahash per second of computing power—hovering between 31 USD and 35 USD per day in November 2026, down sharply from roughly 40.24 USD at the start of October.

November 14’s difficulty drop delivered an estimated 10 percent boost in expected gross revenue per unit of hashrate, offering breathing room against industrial power bills. Yet when those 64,000 machines were pointed toward an attacker’s address on OCEAN, their owners collected nothing for the shares submitted during the hijack window.

For regular investors holding spot Bitcoin or mining stocks, the revenue gap highlights an overlooked business risk. Even though attackers missed out on a full block reward, affected hosting facilities and public miners still owe their utility providers for every minute those machines ran at full tilt without earning a cent for shareholders.

Environmental Impact

Every hijacked ASIC keeps pulling real electricity from the local power grid regardless of whose wallet receives the payout. When 64,000 industrial rigs run under unauthorized pool settings, facilities burn megawatt-hours of electricity and dump waste heat into cooling systems for zero legitimate output, turning productive grid load into pure operational waste.

There is an energy-management twist here as well. Fleet platforms like Luxor Commander are normally installed so operators can automate power targets, pause rigs during peak utility pricing, and balance grid demand in real time. When an attacker gains access to that same remote switchboard, the tools built to trim wasted electricity can be turned against the facility, locking rigs at full draw until local technicians manually sever cloud connections.

Strategic Outlook

This incident did not weaken Bitcoin’s blockchain security, nor did it disrupt transactions for everyday investors. What it did expose is a growing soft spot in how modern mining farms operate: centralizing tens of thousands of rigs behind cloud-connected management agents creates a high-value target for hackers hunting easy hashrate.

Expect hosting providers and public mining companies to tighten network barriers immediately. Isolating local management agents behind hardware firewalls, enforcing strict multi-factor authentication on fleet dashboards, and setting automated alerts for sudden pool-address changes will become standard checklist items for institutional clients before they sign hosting contracts.

Michael Nguyen's take

Losing control of 64,000 rigs through a remote management layer exposes a bigger operational gap than falling Bitcoin prices, in my view. Luxor Technology's pending root-cause review of Commander will reveal whether farms face a software flaw or weak login security. Should attackers ever sustain a redirect long enough to claim block rewards before operators cut the feed, big hosting clients will pull back from centralized dashboards.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.

13 Comments

  1. gigawatt_grim
    64k machines redirected and they still found zero blocks. 13 EH/s sounds huge until you remember the whole network is pushing past 900, these thieves picked the worst possible week for it lol
    1. grizzlywall
      13 EH/s stolen for barely a week against a 900+ EH/s network, expected blocks was basically zero anyway. the math was never on their side
    2. Dragan Mit
      the pool choice being public and traceable is the funniest part. 13 EH of stolen heat pointed at a payout address that doxxes you
    3. segfault_ollie
      routing stolen hashrate to a pool with public payout records is criminal mastermind behavior. the 900 EH network not missing a block is the part that comforts me tho
    4. Sindre Moe
      doxxing yourself via pool payouts while achieving zero blocks, most efficient crime ever. agree the segmentation talk is the actionable bit
  2. Anneli Vesk
    The part that gets me is the attack surface. One remote dashboard layer controlling tens of thousands of ASICs and apparently nobody segmented it. Firmware updates should never share a network path with pool config.
    1. sats_fuse
      hijacking hashrate to OCEAN of all pools is such a weird choice, that payout address is public and traceable. agree with the segmentation point, this was 100% preventable
    2. Nils Back
      Agreed on segmentation. Would add keeping the fleet manager on its own VLAN too, most hosting sites bundle admin and firmware on the same network path. One phish and both fall
    3. portlock_sam
      add immutable logging on the pool config layer too. segmentation stops the push, logs prove which machines got touched before anyone trusts the fleet again
  3. hashbarn_
    64k machines moved with one config push and half the replies are blaming OCEAN itself lol. pool did nothing wrong, whoever left dashboard access open did
  4. vlan_daddy
    firmware updates on 64k machines all checking the same dashboard is the real headline. one credential and you rent the whole fleet for free
    1. bootdisk_bosun
      one dashboard credential steering 64k machines and half these fleets still run shared passwords on stratum endpoints. otp on the pool config wouldve stopped the whole redirect
  5. 0xheattrace
    lost income for a week is bad but the real bill is trust. hosting clients will demand proof of segregated admin networks before renewal now