CyberSIXT reportingUpdated
Bitcoin miner hack hijacked rigs via Luxor's Commander tool
Updated 15 November, 21:08 UTC. The attacker was paid 0.0809 BTC on-chain, and Luxor confirmed a redirect through its Commander tool.
Attackers took control of a large number of Bitcoin mining machines overnight and pointed them at the OCEAN mining pool, with the pool's payouts set to a Bitcoin address they control. Miner hosting company CoreX Hosting raised the alarm at 03:08 UTC on Sunday, warning that "there is a big miner hack going on as we speak" and naming the address, bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr. Posts circulating on X put the total at about 64,000 machines and 13 EH/s of hashrate; that figure has not been confirmed by OCEAN or any operator.
The attacker has now been paid. OCEAN found its next block, number 975995, at 17:20 UTC, and its coinbase transaction sent 0.0809 BTC to the attacker's address, in line with the shares OCEAN's own estimate had credited to it. OCEAN pays miners directly from the block reward, as the developer known as mononaut explained, so the payment could not be held back once the block was found. OCEAN has not commented.
Luxor confirms its fleet tool was used
Mining company Luxor said at 17:25 UTC that its monitoring had alerted it overnight to "an unauthorized redirect of hashrate through Commander", its tool for managing fleets of miners. It said just over a dozen client accounts were affected and their machines were pointed at a different pool for a limited window, that it patched Commander within two hours and began restoring the original pool settings, and that no data was leaked from its systems. Every affected client will be paid in full for the redirected hashrate as if it had mined normally, Luxor said, and it will publish a post-mortem. In a follow-up it said the issue was isolated to Commander and that Luxor Pool and its LuxOS firmware were not affected.
Luxor did not name the pool or the address the machines were sent to, and did not say how the attacker got into Commander. Earlier, CoreX had said the attack was "not a LuxOS thing" and hit "any and all miners, even non-BTC miners", and that it had isolated what I think is the program used.
What the pool data shows
OCEAN's public API showed the attacker's address averaging about 2.8 EH/s over the 12 hours to 12:53 UTC, consistent with several hours at a much higher rate before most machines were taken back; CoreX said at 06:40 UTC that the attack was "over". At 21:07 UTC, 12 machines were still sending about 2.8 PH/s to the address, so some hijacked miners have still not been reclaimed. OCEAN's block list shows the previous block before 975995 was found at 01:00 UTC, before the hijack began.
What miner operators should do
Operators should check every machine's configured pools and payout addresses for bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr or any other unfamiliar address, change the passwords on miners and on any management software that can push configuration to them, and make sure miner web interfaces and management tools are not reachable from the internet. Commander users who were affected should expect contact from Luxor; Luxor says no action is needed from them. Hijacked machines keep running and drawing power, so the loss to operators is the revenue they mined for the attacker while the change went unnoticed.
What is not known
It is not known how many machines or operators were affected in total, whether the Commander redirect accounts for all of them, how the attacker got into Commander, or whether the attacker's address will receive more payouts from the machines still pointed at it.
Sources
- CoreX Hosting on X: miner hack under way, attacker addressPrimary sourcex.com
- Luxor on X: unauthorised hashrate redirect through CommanderPrimary sourcex.com
- Luxor on X: issue isolated to CommanderPrimary sourcex.com
- mempool.space: attacker address, coinbase payout in block 975995Primary sourcemempool.space
- OCEAN API: attacker address shares and estimated earningsPrimary sourceapi.ocean.xyz
- OCEAN API: attacker address hashratePrimary sourceapi.ocean.xyz
- OCEAN API: recent blocksPrimary sourceapi.ocean.xyz
- CoreX Hosting on X: attack overPrimary sourcex.com
More reporting
- Suspected Optimizely breach planted card stealer on 186 websites16 Nov
- BundID cyberattack locks German accounts, email codes now required16 Nov
- Trezor data breach at shipping partner exposes 27,000 orders16 Nov
- Fugaku supercomputer hit by cyberattack, users' SSH keys stolen16 Nov
- Lighter DEX exploit drains $10.4M via a trader's leaked API keys16 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS