Reported Miner Hijack Redirected 13 EH/s to OCEAN; Full Scope Remains Unconfirmed

What happens to a mining operation when its machines are switched to another pool without authorization? In a report published on November 15, 2026, ChainCatcher cited Bitcoin News monitoring that said approximately 64,000 Bitcoin miners, representing 13 EH/s, had been hijacked. Their hashrate was reportedly directed to the OCEAN pool, with payouts assigned to a Bitcoin address controlled by the attacker.

The attack reportedly began at around 8 p.m. US Central Time. OCEAN’s dashboard showed its hashrate briefly approaching 50 EH/s before falling to about 40 EH/s. Those are pool-wide readings, not a measure of what any individual operator lost.

Reported Miner Hijack Redirected 13 EH/s to OCEAN; Full Scope Remains Unconfirmed (1)

CoreX Hosting first alerted operators to unauthorized pool changes. One affected operator said its entire mining facility had been hijacked and identified Luxor’s Commander miner-management software as the source of the security incident. Other operators reported similar unauthorized pool changes several days earlier. Whether Luxor Commander was compromised has not been independently confirmed.

Reported Miner Hijack Redirected 13 EH/s to OCEAN; Full Scope Remains Unconfirmed (2)

CoreX later said the attack appeared to have ended, with the redirected hashrate falling from 13 EH/s to roughly 100 PH/s. The attacker reportedly found no Bitcoin block during the hijack and therefore received no block reward. Affected miners nevertheless permanently lost the opportunity to earn Bitcoin during that period. The incident’s full scope remains unconfirmed.

Source: chaincatcher.com (originally published 2026-11-15 19:23 UTC+8)

Further reading