Blackmint

From the Blackmint News archive. Prices and details may have changed since publication.

Blackmint Desk · Bitcoin · Nov 15, 2026

Luxor Says Commander Breach Redirected Clients' Bitcoin Hashrate

Just over a dozen client accounts were hit, and Luxor will pay them as if their machines had mined normally. It hasn't said how the attacker got in.

Bitcoin mining firm Luxor said on Sunday that someone used its Commander fleet software to point machines in more than 12 client accounts ("just over a dozen," it said) at a different mining pool, and it patched the hole within two hours.

"Every affected client will be paid in full for the redirected hashrate, as if it had mined normally," Luxor said in a statement on X, quoted by Bitcoin.com News and The Defiant. The statement gave no payment date, total amount or method of calculation.

Why one setting decides the payout

A mining machine does the work, but a pool address set on each machine decides where that work is credited. The pool then pays rewards to the owner's payout address. Change the pool setting and the machine keeps running at full power while the rewards go to someone else. Luxor's product page says Commander can change pool settings on thousands of miners in one operation, The Defiant reported.

What Luxor said it fixed

Luxor said its monitoring caught the redirect overnight, and engineers then began restoring machines to their original pools. The company said Luxor Pool and its LuxOS firmware were not affected and that no data was leaked or taken from its systems. Commander is operating normally, users need to take no action, and a full post-mortem will follow, Luxor said. It gave no date.

What still isn't known

Luxor hasn't said how the attacker got in or how many machines were involved. Mining host CoreX Hosting reported about 13 exahashes per second, a measure of computing power, at the address it tied to the attack, according to The Defiant and Bitcoin.com News. Luxor hasn't confirmed that figure.

A block found by the OCEAN pool paid about 0.0809 BTC to that address, per on-chain records cited by CryptoWatchDesk and The Defiant. OCEAN pays every address with recent work when any pool member finds a block. We found no statement from OCEAN on whether it will act on that payout.

In our opinion: the weak point here wasn't a pool or a wallet but the dashboard that tells thousands of machines where to send their work. Luxor's pledge covers the clients, but the post-mortem is what other fleet operators need, because it should explain the way in. Until it's published, the 0.0809 BTC sitting at that address is the only payout anyone can see on-chain.

Sources: Bitcoin.com News: Luxor confirms Commander incident (quotes Luxor's X statement) · The Defiant: Luxor Pledges Full Compensation for Commander Hijack · The Defiant via Cryptonews.net (full text): Luxor Pledges Full Compensation for · CryptoWatchDesk: Luxor confirms Commander hijack; OCEAN paid attacker address

Revisions

First published .

No revisions since publication.

We fix errors and say so. See every correction on the Blackmint corrections page.

Open in Blackmint →Blackmint · blackmint.markets · Not financial advice.