CoinSnif

OCEAN reports mining-pool settings changed on roughly 64,000 Bitcoin miners

What happens when a miner’s pool settings are changed without authorization? In a report published November 16, 2026, at 03:53 UTC+8, Odaily said OCEAN had observed roughly 64,000 Bitcoin miners, representing about 13 EH/s, redirected to its pool. The incident reportedly began at around 8 p.m. U.S. Central time; the report did not establish an exact calendar date for that start time.

OCEAN reported that its pool hashrate briefly reached about 50 EH/s, then stabilized near 40 EH/s. The redirected hashrate later fell to roughly 100 PH/s as most affected machines were quickly returned to their prior settings or went offline. These are pool-level measurements, not estimates of any individual operator’s output.

According to the report, any mining proceeds from the redirected machines were set to go to a single attacker-controlled payout address. The attacker did not mine a block, so that address received no payment. The report said affected miners could not recover the mining income they lost during the disruption; it did not quantify that loss.

Hosting provider CoreX Hosting was the first to notify an operator after finding unauthorized changes to affected machines’ pool settings. One operator said its entire mining operation was affected and suspected Luxor Commander, mining-fleet management software, 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, raising the possibility that this was not an isolated incident.

The reported failure was in the operational software connecting mining companies to their hardware. Bitcoin’s protocol and consensus rules were not compromised.

Source: odaily.news (originally published 2026-11-16 03:53 UTC+8)

Further reading