#据报约6.4万台比特币矿机遭劫持 6.4 million mining rigs “seized”? I dug up the manufacturer’s statement: they were hijacked, and full compensation has already been promised. In my view, this is just an excuse for the sharp drop

The headline says “seized,” which sounds like a law-enforcement raid. I compared the accounts from all three parties: it was a hijack that changed mining-pool settings; Luxor has confirmed this and promised full compensation.

📊 Key data
· Mining-pool settings were changed without authorization and hash power was redirected; this was not a seizure. It began at 20:00 CT on 11/14
· About 13 EH/s was redirected to OCEAN; its hash rate fell from nearly 50 to about 40 EH/s
· The “64,000 rigs” figure is unverified; Luxor mentioned only a dozen or so accounts
· CoreX said at 01:40 on 11/15 that it appeared to have ended; the tagged address fell to about 100 PH/s (-99%)
· The attacker mined no blocks and the address received no payments; the protocol was not compromised

🔍 Key contradictions
One: This was a hijack, not a seizure; middleware, not the protocol. The attacker neither impounded the rigs nor tampered with the network. They only changed the pool configuration and payout address; block production continued normally. As with the 11/14 Tor vulnerability, the risk lies at the configuration layer.
Two: “64,000 rigs” and “13 EH/s” have different levels of credibility. Hash rate can be checked, but pool records cannot establish the number of rigs; 64,000 is a media figure that has not been independently verified. Officials mentioned only a dozen or so customer accounts.
Three: The attacker didn’t get a penny. No blocks were mined while the hash rate was on OCEAN, and the address received no payments; about 0.6576 BTC is only an estimate, not a payment. The earlier claim that the funds “could not be recovered” has been superseded by the compensation.

🧊 Three reality checks
1. Don’t mistake “hijack” for “seizure.” The protocol wasn’t compromised, and the attacker didn’t even mine a block.
2. 64,000 rigs is not a confirmed figure. Hash rate can be checked; the number of rigs has not been verified.
3. Don’t blame this for the sharp drop. The price pressure came from liquidations of multi-billion-dollar long positions, ETF outflows, and 10Y yields at 5%.

💡 My take
The key issue is centralization of the control plane: a single piece of software can redirect more than ten EH/s. A pool can spot abnormal hash rates, but it’s difficult to block them at the payout-address level. The company described it as an “AI-assisted attack vector,” but that has not been verified.
What to do: If you operate mining rigs, check your configuration and wait for the postmortem; holders don’t need to do anything.

⚠️ Not investment advice. Refer to Luxor’s statement for details.
Should mining farms decentralize their management software or keep it centralized? Let’s discuss in the comments 👇
Follow @阿Sue的加密日记 · Using data to expose false signals in crypto
#Bitcoin #MiningRigs #Cybersecurity