Ocean Mining denies involvement in Luxor pool hack after AI‑driven hashrate hijack
Ocean Mining says its payout system was not compromised and rejects claims it profited from the Luxor Commander hack that redirected miners’ rewards.
Key takeaways
- Ocean Mining asserted its systems were unaffected and that its non‑custodial payout model cannot be used to block or reassign rewards.
- Luxor’s Commander tool was exploited by an AI‑enabled vector, redirecting hashrate from over a dozen client accounts for a short period before being patched.
- Luke Dashjr alleged Ocean collected roughly 0.01 BTC in fees from the compromised mining activity, a claim the pool disputes.
Ocean Mining issued a public statement on X denying any role in the recent cyber‑incident that affected Luxor’s Commander fleet‑management software. The pool said its infrastructure operated normally throughout the attack and that its permission‑less, non‑custodial payout system could not have been used to divert rewards to attackers, countering accusations made by Bitcoin developer and former Ocean chairman Luke Dashjr.
Luxor’s AI‑enabled breach
According to Decrypt, hackers exploited a vulnerability in Luxor’s Commander tool on Saturday evening, briefly redirecting the hashpower of more than a dozen client accounts to an external mining pool. The redirection lasted only minutes before Luxor’s internal monitoring flagged the activity and a patch was applied within two hours. The company reported no data loss and pledged full compensation for the affected miners, stating that the compromised hashpower will be treated as if it had mined normally.
Ocean’s defense of its payout model
Ocean Mining’s response centers on its TIDES payout system, which it describes as automatically crediting valid proof‑of‑work without assessing equipment ownership. The pool argues that once work is verified, the associated reward cannot be reassigned under its rules, and that any attempt to block or redirect payouts would undermine Bitcoin’s permissionless design. “Bitcoin is either permissionless or it is not. There is no middle ground,” the statement read.
Dashjr’s profit allegations
In a separate post, Luke Dashjr claimed Ocean instructed miners to send 0.16202083 BTC (about $10,500) to the attackers after the breach became public, and that the pool continued to allocate a further 0.08123485 BTC (≈$5,270). He also cited pending payouts of 0.33029017 BTC (≈$21,400) and asserted that Ocean had already collected 0.00330655 BTC in fees and stood to earn another 0.00660580 BTC, totaling roughly $650. Ocean did not directly address these figures, instead emphasizing the principle that its system cannot retroactively reassign rewards.
What to watch next
The incident highlights growing concerns over AI‑driven attacks on mining infrastructure. Luxor plans to publish a detailed post‑mortem, while Bitcoin Core has updated its security policy to address similar threats. Observers will be monitoring whether any regulatory bodies examine the responsibilities of mining pools in such attacks and whether Ocean Mining’s payout architecture faces further scrutiny.
Frequently asked questions
What was the method used in the Luxor hack?
Luxor’s CEO said the breach was carried out through a sophisticated AI‑enabled vector that temporarily redirected mining hardware to another pool.
Can a mining pool block payouts from compromised work?
Ocean Mining argues its non‑custodial TIDES system automatically credits valid proof‑of‑work and cannot retroactively block or reassign rewards.
Sources
Get stories like this in your inbox
The day’s biggest crypto stories and market moves in one short morning email. Free, no spam.