AdvertiseFee Deal Desk

Bitcoin

Luxor Patches Commander 2 Hours After Bitcoin (BTC) Mining Hijack Rerouted 13 EH/s

Luxor patched Commander within two hours after a Bitcoin (BTC) mining hijack redirected 64,000 machines and 13 EH/s to an attacker's pool.

Be a creator
November 16, 2026, 01:28 AM UTC4 min read
AI SummaryAI
  • CoreX Hosting reported about 64,000 miners and 13 EH/s of hashpower redirected during the attack.
  • Block 975,995 paid 0.08088977 BTC to the attacker's address on Nov 16.
  • Hashpower linked to the hacker's address fell to about 100 PH/s before the attack ended.
  • Luxor confirmed more than 12 Commander customer accounts were affected and no data leaked.
eToro

Luxor Applies Emergency Patch

Luxor applied a security patch within two hours of detecting the hijack that diverted its fleet-management customers' hashpower, and says it will reimburse every affected account in full for rewards lost during the incident. CoreX Hosting, a provider of hosted crypto mining capacity, flagged the attack publicly on Sunday and later confirmed it had ended, yet a payout still reached the attacker's wallet even after that announcement: roughly 7 million South Korean won at Bitcoin (BTC) price levels early on Monday.

The hosting company said in a post on X on 2026-11-15 that a large-scale compromise of mining machines was underway and that the affected devices were being pointed at a single Bitcoin (BTC) address on the OCEAN mining pool. Its estimate at the time stood at about 64,000 machines, with roughly 13 exahash per second (EH/s) of hashpower switched without the owners' consent. Hashpower is the computing capacity committed to Bitcoin mining, and its redirection matters for a simple reason: when a machine's configuration is altered so that its reward address belongs to an attacker, block rewards that should reach the legitimate operator are paid elsewhere. CoreX Hosting reported that the attack ended about three and a half hours after its first warning, by which point the hashpower still connected to the hacker's address had fallen to roughly 100 petahash per second (PH/s). The company identified the receiving address in that first alert, and it is the same address that collected Monday's payout, tying the on-chain record directly to the incident CoreX described. Neither CoreX Hosting nor Luxor has explained how the configuration changes spread across so many machines, and neither has published the total number of miners actually touched. Luxor's reimbursement pledge covers the diverted hashpower, though the company has not yet quantified the total value owed.

On-chain data confirms the money moved after the shutdown. Block 975,995, generated in the early hours of Monday, 2026-11-16, paid 0.08088977 Bitcoin (BTC) to the address CoreX Hosting had singled out in its alert, according to Bitcoin blockchain records. The payment exists because of how the OCEAN pool settles earnings: it distributes rewards based on the hashpower a participant contributed over a defined window, so mining work submitted during the attack still qualified for shares of blocks the pool found later. In practice, the hijacked machines' submitted work translated into real payouts on blocks mined after CoreX declared the incident closed.

Luxor has since acknowledged its own role in the breach. The company said in an official statement that more than 12 customer accounts on its Commander platform were affected. Commander is a fleet-management tool that lets operators control large groups of miners remotely, including the pool connections whose settings were changed during the attack. Luxor said it began applying a security patch and restoring miner configurations within two hours of detecting the incident. It also stated that no data leaked from its systems, and committed to paying affected customers compensation equal in value to the full hashpower that was diverted. What remains undisclosed is substantial. The exact number of machines affected, the precise intrusion path into Commander, and the aggregate value of rewards paid to the attacker have not been confirmed by either Luxor or CoreX Hosting. CoreX's own accounting stops at estimates: the 64,000-machine figure and the 13 EH/s reading were both presented as assessments made while the attack was still running, not as audited totals. OCEAN's payout rules, not any action by the pool, determined where the diverted work was settled.

The financial tail of this attack extends past containment, because a pool that settles rewards on a rolling window keeps paying for work submitted before the patch. Luxor's fix and its full-reimbursement pledge cover customers' losses on paper, but the company has not yet named the intrusion path or the final machine count, so the response leaves the root cause unaddressed. The receiving address is a payout wallet rather than a crypto whale position; its credit of 0.08088977 Bitcoin (BTC) reflects diverted work, not accumulation. The episode also shows how fleet-management software has become a single point of failure in proof of work operations: one compromised dashboard moved an estimated 64,000 machines at once. Until Luxor publishes a full post-mortem, hosted miners have little beyond the patch to judge the risk.

COINOTAG's editorial and research desk.

AI-Assisted

AI-generated, AI-reviewed, under COINOTAG editorial oversight.