Attacker cashed out 0.162 BTC from OCEAN pool without mining any blocks
An attacker hijacked thousands of mining rigs and redirected their output to the OCEAN pool, receiving over $10,000 in rewards without solving a single block, a vulnerability that exposes how mining pools automatically pay out based on historical work, not actual block finds. The incident reveals a fault line in pool design between automation and security that will test whether pools can balance censorship resistance with customer protection.
- Attacker hijacked approximately 64,000 mining machines representing 13 exahashes per second of hashrate via Luxor’s Commander software on November 15, 2026
- OCEAN paid the attacker’s address 0.162 BTC (over $10,000) across two block rewards despite the attacker finding zero blocks themselves
- Pool paid rewards because OCEAN automatically distributes shares to all addresses in its reward window when blocks are found, even after machines disconnect
- 64,000 Mining machines compromised in the weekend attack, per CoreX Hosting alert
- 0.162 BTC Total paid to attacker across two block payouts, worth approximately $10,500
- $650 Fees retained by OCEAN from the incident, according to former co-founder Luke Dashjr
A remote compromise of Luxor’s Commander fleet-management software allowed attackers to hijack thousands of mining rigs over the weekend and point their hashrate at OCEAN, a Bitcoin mining pool, with payouts directed to a single attacker-controlled address. CoreX Hosting first reported the breach on X (formerly Twitter), putting the damage at approximately 64,000 machines and roughly 13 exahashes per second of hashrate. Luxor confirmed the flaw ran through its Commander software and said the compromised machines belonged to just over a dozen client accounts. The company patched the vulnerability quickly and pledged full compensation to affected customers, though the pool’s broader infrastructure and user data remained secure.
Luxor CEO Nick Hansen attributed the breach to “a sophisticated AI-enabled vector” but did not disclose the specific attack mechanism.
OCEAN paid attacker $10,500 via automatic share distribution despite zero blocks mined
The attacker’s machines never solved a block during the hijack. Yet when OCEAN subsequently found two blocks, OCEAN’s statistics page shows the attacker’s address received payouts totaling 0.162 BTC, worth more than $10,500. This occurred because OCEAN pays miners for their recent work whenever the pool finds a block, automatically distributing rewards to all miners whose shares remain in the pool’s reward window, regardless of whether those miners are currently active or contributed to the block that triggered the payout.
Galaxy’s head of research Alex Thorn tracked the payouts on-chain and noted that a second payout of 0.081131 BTC (approximately $5,000) was sent moments after the first.
Former OCEAN co-founder Luke Dashjr, a longtime Bitcoin Knots developer who left the pool in August over a disagreement on BIP-110 protocol direction, claimed the attacker was scheduled to receive an additional $21,400 in payouts over the following 24 hours.
Once the attacker’s shares dropped out of OCEAN’s reward window, Thorn estimated approximately one and a half days after the hijack began, all further payouts would cease.
Dashjr also calculated that OCEAN retained nearly $650 in fees from transactions associated with the attack.
Dashjr accuses OCEAN of choosing automation over customer protection
Dashjr argued that OCEAN could have prevented the payout by blocking the attacker’s address once the breach became public. He contended the pool had adequate notice to deny the attacker any reward before the blocks were mined and payouts distributed.
“OCEAN is profiting from a cyberattack on their own customers, and rewarding the attackers,” Dashjr posted on X, framing the incident as a failure of pool governance rather than technical inevitability.
Not all observers agreed with this interpretation. One user countered that refusing to filter the address would demonstrate Bitcoin’s censorship resistance in action, and noted that Luxor’s commitment to fully compensate affected miners meant customers bore no financial loss. OCEAN had not publicly responded to Dashjr’s accusations at the time of reporting.
The core question remains unresolved: whether a pool should prioritize automatic, indiscriminate payment processing for privacy and philosophical reasons, or retain discretionary control to block known attackers when security events occur.
This mirrors the broader debate over transaction filtering and demonstrates why pool design matters more as large operators consolidate hashrate.
The CCS read. Institutional miners now face a concrete tradeoff in pool selection: fully non-custodial pools that enforce censorship resistance automatically may also automatically pay attackers, while pools retaining manual controls accept some centralization risk to block bad actors. Luxor’s customer compensation pledge shifts the actual loss to the operator, not the miner, but leaves pools with no good choice between ideological purity and practical security. The question OCEAN has not answered is whether that $650 in fees justifies inaction.
OCEAN must clarify whether it will implement automatic address blocking in future security events and, if not, explain the threshold at which it would exercise discretionary controls. Until then, mining operators evaluating fleet software should demand that their hosting providers and pool partners publish explicit policies on attack response and share-window cutoffs in their terms of service.