The hijack of 64,000 Bitcoin miners did pay: OCEAN’s next block sent the attacker 0.0809 BTC
PublicAML · On-chain investigation · 15 November 2026
Overnight on 14–15 November someone repointed about 64,000 Bitcoin mining machines, roughly 13 EH/s, to the OCEAN pool with payouts to an address of their own. The early reports said the attackers mined no blocks and earned nothing. That was true until 17:22 UTC. OCEAN found block 975995, and its coinbase transaction paid the attacker’s address 0.08088977 BTC, about $5,250, as one of seventeen miners in the block. The coins are locked by Bitcoin’s rules until block 976095, so they cannot move before about 10:00 UTC on 16 November. We are watching the address.
0.08088977 BTC
paid to the attacker’s address in OCEAN block 975995, 15 Nov 2026, 17:22 UTC (≈ $5,250)
2.58%
the attacker’s share of that block’s 3.1319 BTC reward
block 976095
earliest block in which the coinbase coins can be spent (100-block maturity)
0
payments to this address before 17:22 UTC; OCEAN’s previous block (01:00 UTC) did not include it
Contents
What was reported
CoreX Hosting raised the alarm first: machines at its sites had been switched to another pool without authorization. Reports put the total at about 64,000 machines and 13 EH/s, all pointed at OCEAN, a non-custodial pool that pays miners directly in the block’s coinbase transaction. OCEAN’s public hashrate briefly approached 50 EH/s, then the hijacked power fell to about 100 PH/s. One operator pointed at fleet-management software as the way in; that is not confirmed. Several outlets reported that the attackers “failed to mine blocks” and that the address had received nothing.
The payout
OCEAN found its previous block, 975869, at 01:00 UTC on 15 November, before the hijack began; its coinbase has eighteen outputs and none of them is bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr. The next OCEAN block, 975995, came at 17:22 UTC. Its coinbase pays 3.1319 BTC to seventeen addresses, and one of them is the attacker’s: 0.08088977 BTC, 2.58% of the block. The address has exactly one transaction, this one.
| When (UTC) | From | To | Amount | Tx |
|---|---|---|---|---|
| 15 Nov 17:22 | OCEAN bl…nbase) | bc1qphuk…pcddrr | 0.08088977 BTC (2.58% of the block reward) OCEAN pays miners in the coinbase; spendable from block 976095 | 07ff9e20…ef98d1 |
Why it may not be the last one
OCEAN does not pay for a single block. Its TIDES scheme splits each block’s reward among the shares submitted over a window several blocks’ worth of work long, so shares from the hours of the hijack stay in that window after the hashrate is gone. Until they slide out, each OCEAN block can pay this address again. We will add any further payouts here.
Coinbase coins cannot be spent until 100 more blocks are mined. For block 975995 that is block 976095, around 10:00 UTC on 16 November. Whatever the attacker does with this money will show from then on. The owners of the hijacked machines lost the revenue they would have earned in those hours; the amount paid to the attacker is a small part of it.
What this page does not say
It does not say who the attacker is, how the machines were taken over, or that OCEAN, CoreX Hosting, any software vendor or any hosting operator did anything wrong. The machine count, hashrate and timing come from CoreX Hosting and the press; the payout, its share and the block data are on chain and anyone can check them.
Addresses in this case
Payout address the hijacked miners were set to (attacker); 0.0809 BTC from OCEAN, unspent
Check an address yourself
Free, no sign-up. Paste any address to see whether it is linked to this or any other incident:
Sources: CoreX Hosting via Bitcoin News, KuCoin News, Crypto Briefing and Blockonomi (15 Nov 2026) for the scale and timing; Bitcoin blocks 975869 (coinbase 35aeab0c72ef3c8d…) and 975995 and the address history via mempool.space; BTC price $64,919 (mempool.space, 15 Nov 2026, 19:40 UTC). Balances checked 15 Nov 2026, 20:05 UTC.
