What happens when miners keep running but their pool settings change without authorization? In a report published November 15, 2026, at 19:23 (UTC+8), ChainCatcher cited Bitcoin News monitoring that said roughly 64,000 Bitcoin miners, representing 13 EH/s, had reportedly been redirected to the OCEAN pool. Payouts were designated for Bitcoin addresses controlled by the attacker, according to the report.
The attack reportedly began at around 8 p.m. US Central time; the source does not specify the calendar date for that 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 any individual operator’s losses.
CoreX Hosting first raised the alarm, saying miners had been switched to another pool without authorization. One affected operator said its entire facility had been hijacked and identified Luxor’s Commander miner-management software as the source of the incident. Other operators reported similar unauthorized pool changes days earlier. Whether Luxor Commander was compromised has not been independently confirmed, nor has the incident’s full scope.
CoreX later said the attack appeared to have ended, with the redirected hashrate falling from 13 EH/s to approximately 100 PH/s. The attacker reportedly found no Bitcoin block during the hijack and therefore received no block reward. Affected miners nevertheless lost the opportunity to earn Bitcoin during that period.
Source: chaincatcher.com (originally published 2026-11-15 19:23 UTC+8)


