In 30 seconds

A mass hijack of Bitcoin mining machines appears to have ended with a whimper: CoreX Hosting, the firm that first raised the alarm, reported the diverted hashrate collapsing from 13 EH/s to roughly 100 PH/s, and the attackers failed to mine a single block, so no block rewards were collected.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
The headline numbers, still estimates: about 64,000 machines and 13 EH/s of computing power, meaning 13 quintillion hash attempts per second, reportedly redirected to the OCEAN mining pool with payouts steered to a Bitcoin address said to be controlled by the attackers. Reports put the start around 8 PM CT on November 14.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source listCointelegraphx.com · Cointelegraph · xOpen original sourceSee in source list
What happened
The first public warning came from CoreX Hosting, a mining host, posting mid-attack that 'there is a big miner hack going on' and that machines were being pointed at OCEAN under the Bitcoin address bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr.CoreX_Hostingx.com · CoreX_Hosting · xOpen original sourceSee in source list
One affected operator says an entire farm was taken over and has blamed Luxor's Commander mining management software as the source of the compromise. Other operators reported similar unauthorized pool changes several days earlier, which hints the incident may be broader than a single night.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source listBitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
CoreX later reported that the attack appeared to be over, with the hijacked hashrate falling from 13 EH/s to about 100 PH/s. The full scope, and whether Luxor Commander was actually compromised, remains unconfirmed.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
Why it matters
For the machine owners this was pure loss. Their hardware kept burning electricity while credit for the work went elsewhere, and unlike stolen coins, hashing time cannot be recovered or refunded.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source listCointelegraphx.com · Cointelegraph · xOpen original sourceSee in source list
The suspected entry point matters beyond this incident. If fleet management software like Luxor Commander can quietly rewrite pool settings on thousands of machines, every operator using similar tools has to assume their payout configuration is only as safe as that software.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
What to do
If you run mining hardware, audit pool settings and payout addresses on every machine, not just a sample, and rotate the passwords and API keys for whatever management software controls the fleet. Anyone using Luxor Commander should treat it as suspect until Luxor or an independent party clears it.CoreX_Hostingx.com · CoreX_Hosting · xOpen original sourceSee in source listBitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
Confirmed and still uncertain
Established so far: CoreX posted a live warning naming a specific payout address, OCEAN's dashboard visibly spiked, and the surge then faded. Cointelegraph and BitcoinNewsCom both reported the 64,000 machine and 13 EH/s figures.CoreX_Hostingx.com · CoreX_Hosting · xOpen original sourceSee in source listCointelegraphx.com · Cointelegraph · xOpen original sourceSee in source list
Still unknown: how the attackers got in, whether Luxor Commander was the actual source, how many farms were hit, and who is behind it. Nothing in the public record yet amounts to independent confirmation of the scope, and by all accounts no block reward was paid during the hijack window.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
What people are saying
BitcoinNewsCom, which assembled the timeline, also worked the replies as the story spread, calling it the 'worst theft effort in history' after the attackers came away empty, and describing the situation as 'very scary' and 'very worrying'.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source listBitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source listBitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
The same account relayed ground truth from operators: one farm operator said all of his machines were hijacked and that other farms were hit too. Cointelegraph's own alert echoed the machine count and hashrate figures.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source listCointelegraphx.com · Cointelegraph · xOpen original sourceSee in source list
Evolution
The story sharpened in stages. CoreX fired off a live warning with a payout address while machines were still being redirected. Aggregated reporting then sized the event at 64,000 machines and 13 EH/s, tied the start to about 8 PM CT on November 14, and surfaced the Luxor Commander lead. By the time Cointelegraph posted its alert, one point had settled: the hijackers never mined a block.CoreX_Hostingx.com · CoreX_Hosting · xOpen original sourceSee in source listBitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source listCointelegraphx.com · Cointelegraph · xOpen original sourceSee in source list
The unresolved thread is time. Reports of unauthorized pool changes several days before the November 14 wave suggest this may be one visible piece of a longer campaign rather than an isolated overnight event.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
Reach
3 independent groups, 3 updates, and 2275 engagements.
Technical detail
The method, as described, required no breakthrough cryptography: pool settings were rewritten so machines kept hashing but credited their work to OCEAN under the single address bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr. The suspected weak point is Luxor Commander, software operators use to manage fleets of machines remotely.CoreX_Hostingx.com · CoreX_Hosting · xOpen original sourceSee in source listBitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
Pools pay miners through block rewards and share-based payouts, so whoever controls the payout address controls the money. In this case the attackers reportedly found no block during the hijack, which is why the address apparently collected nothing despite commanding 13 EH/s.Cointelegraphx.com · Cointelegraph · xOpen original sourceSee in source listBitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
Sources and evidence
The record so far is social posts, not incident reports. CoreX Hosting, a hosting provider caught mid-attack, supplied the original warning and the payout address. BitcoinNewsCom assembled the timeline, including the Luxor Commander attribution and the wind-down figures. Cointelegraph independently repeated the 64,000 machine and 13 EH/s numbers.CoreX_Hostingx.com · CoreX_Hosting · xOpen original sourceSee in source listBitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source listCointelegraphx.com · Cointelegraph · xOpen original sourceSee in source list
Handle with care. The machine count is an estimate, the Luxor Commander link comes through one operator quoted secondhand, and nothing has been independently verified about the breach itself. OCEAN's role deserves nuance too: a mining pool is open by design, and hashrate pointing at it is not evidence the pool was compromised.BitcoinNewsComx.com · BitcoinNewsCom · xOpen original sourceSee in source list
Sources
- BitcoinNewsComx.com · BitcoinNewsCom · x
- Cointelegraphx.com · Cointelegraph · x
- CoreX_Hostingx.com · CoreX_Hosting · x
- BitcoinNewsComx.com · BitcoinNewsCom · x
- BitcoinNewsComx.com · BitcoinNewsCom · x
- BitcoinNewsComx.com · BitcoinNewsCom · x
- BitcoinNewsComx.com · BitcoinNewsCom · x



