At 8 p.m. on November 14, rigs at several mining farms in the U.S. Midwest were still running, but the proceeds were already going to someone else’s address.
The OCEAN dashboard lit up first: around 64,000 Bitcoin mining machines, representing roughly 13 EH/s of hashrate, had been redirected to OCEAN, and their payout address had been changed to one controlled by the attacker. CoreX Hosting was the first to raise the alarm: its machines’ mining pool settings had been changed without authorization. OCEAN’s hashrate briefly surged to nearly 50 EH/s before dropping back; by the 15th, it was down to around 100 PH/s.
The absurd part: the attacker mined no blocks overnight, and that address received not a cent. The miners still paid their electricity bills and kept their machines running, but the coins that this hashrate should have produced during that time are gone forever.
Three mechanisms are worth unpacking.
First, the attacker didn’t change the private keys, but three settings: the mining pool address, the payout address, and the management console. The attacker didn’t touch the Bitcoin network; they targeted the control plane between the mining farm and its machines. The protocol remained intact; the middleware was compromised.
Second, 13 EH/s wasn’t enough to find a block. Over the past two weeks, the network’s total hashrate has fallen from above 1,000 EH/s. At around 1.3% of the total, 13 EH/s had little chance of finding a block in the first place—and it was pulled back soon after. Not finding one was the norm.
Third, the point of entry wasn’t on-chain. One operator named Luxor’s Commander management software, but this has yet to be independently verified. However, reports of unauthorized mining pool switches had already surfaced in the days before the 14th, which looks more like a test run ahead of a broader takeover.
If you’ve dealt with hosted mining machines, cloud hashrate, or mining pool accounts, here are three questions to ask now: Who besides you can change the payout address? Does the management console have two-factor authentication and an IP allowlist? If hashrate is interrupted or earnings are abnormal, who is responsible under the contract? Bulk management software is inherently a single point of failure: one compromised password, and an entire mining farm can be taken over at once.
Should this be considered a platform security failure, or a failure by the operators to manage permissions properly?
$BTC $ETH
This article is for informational and educational purposes only and does not constitute investment advice.
Sources: OCEAN pool monitoring, BlockBeats, Odaily (2026-11-15); Bitcoin News; Bitcoin.com.
The OCEAN dashboard lit up first: around 64,000 Bitcoin mining machines, representing roughly 13 EH/s of hashrate, had been redirected to OCEAN, and their payout address had been changed to one controlled by the attacker. CoreX Hosting was the first to raise the alarm: its machines’ mining pool settings had been changed without authorization. OCEAN’s hashrate briefly surged to nearly 50 EH/s before dropping back; by the 15th, it was down to around 100 PH/s.
The absurd part: the attacker mined no blocks overnight, and that address received not a cent. The miners still paid their electricity bills and kept their machines running, but the coins that this hashrate should have produced during that time are gone forever.
Three mechanisms are worth unpacking.
First, the attacker didn’t change the private keys, but three settings: the mining pool address, the payout address, and the management console. The attacker didn’t touch the Bitcoin network; they targeted the control plane between the mining farm and its machines. The protocol remained intact; the middleware was compromised.
Second, 13 EH/s wasn’t enough to find a block. Over the past two weeks, the network’s total hashrate has fallen from above 1,000 EH/s. At around 1.3% of the total, 13 EH/s had little chance of finding a block in the first place—and it was pulled back soon after. Not finding one was the norm.
Third, the point of entry wasn’t on-chain. One operator named Luxor’s Commander management software, but this has yet to be independently verified. However, reports of unauthorized mining pool switches had already surfaced in the days before the 14th, which looks more like a test run ahead of a broader takeover.
If you’ve dealt with hosted mining machines, cloud hashrate, or mining pool accounts, here are three questions to ask now: Who besides you can change the payout address? Does the management console have two-factor authentication and an IP allowlist? If hashrate is interrupted or earnings are abnormal, who is responsible under the contract? Bulk management software is inherently a single point of failure: one compromised password, and an entire mining farm can be taken over at once.
Should this be considered a platform security failure, or a failure by the operators to manage permissions properly?
$BTC $ETH
This article is for informational and educational purposes only and does not constitute investment advice.
Sources: OCEAN pool monitoring, BlockBeats, Odaily (2026-11-15); Bitcoin News; Bitcoin.com.
