An exploit of a third-party mining management tool briefly diverted about 64,000 bitcoin mining machines, pushing up to 13 exahashes per second — roughly 1.4% of the network’s hashrate — toward a single unauthorized payout address on the OCEAN pool.
CoreX Hosting flagged the activity on November 14, warning that thousands of machines had begun connecting to OCEAN under one external address, and said it was working to restore the affected rigs’ original configurations. By 1:40 a.m. ET on November 15 the host reported the attack contained: hashrate pointed at the rogue address had fallen from 13 EH/s to about 100 petahashes per second.
Mining services company Luxor confirmed the following day that its Commander fleet-management software had been exploited to reassign pools. It said internal monitoring detected unauthorized reassignments across “just over a dozen” client accounts, that engineers patched the vulnerability within two hours, and that no user data leaked. Its core mining pool and LuxOS firmware were unaffected.
The economics were modest for the scale of the hijack. Trackers initially noted the attacker mined no block during the window. OCEAN’s payout model nonetheless left a residue: valid shares submitted while a round is active remain eligible when the pool subsequently finds blocks, and the address received between 0.162 BTC and 0.243 BTC across two to three rewards, worth roughly $10,500 at current prices.
The cost fell on operators. Affected miners lost revenue during the outage while continuing to pay for power, and the episode exposed how much authority fleet-management software holds over where a machine points its work. A console that can reassign pools for thousands of rigs is a single point of failure with no on-chain signature requirement.
Nothing about Bitcoin’s consensus was tested. Reaching 1.4% of hashrate is far below the threshold needed to reorder or censor blocks, and no invalid chain was produced. The failure mode was operational — hijacked machines still mined valid bitcoin, just for someone else’s address.
The reporting describes the exploit as AI-assisted. For hosting providers, the practical lesson is narrower than protocol design: credentials and control paths into miner fleets deserve the same scrutiny as exchange keys, because the software sits between thousands of machines and the pool they pay.