In a report published on November 16, 2026, OCEAN said it had detected roughly 64,000 Bitcoin mining machines whose hashpower was redirected to the OCEAN pool. It estimated the redirected capacity at about 13 EH/s. The incident began around 8 p.m. US Central time; the report did not establish a date for that time.
OCEAN said its pool’s hashpower briefly reached about 50 EH/s, then stabilized near 40 EH/s. The redirected capacity later fell to about 100 PH/s as most affected machines were quickly restored or went offline.
What changed? CoreX Hosting, the hosting provider that first alerted an operator, said it had found unauthorized changes to the affected machines’ pool settings. According to the report, the redirected mining output was assigned to a single attacker-controlled payout address. The attacker did not mine a block, so that address received no payment. The report said the affected miners’ lost income could not be recovered.
One operator said its entire mining operation was affected and suspected Luxor Commander, a fleet-management tool, as a possible entry point. That connection was not confirmed. Reports of unauthorized pool-setting changes had also surfaced in the days before November 14, suggesting the incident might not have been isolated.
The reported failure involved software connecting mining companies to their hardware—not Bitcoin’s protocol or consensus rules.

