Loading market data...

Luxor Says Hijacked Bitcoin Miners Had Rewards Redirected to Attacker

Luxor Says Hijacked Bitcoin Miners Had Rewards Redirected to Attacker

Luxor has confirmed that bitcoin miners on its platform had their block rewards redirected to an attacker after their machines were hijacked. The mining pool operator says the affected rigs were pointed at a different mining pool entirely, sending payouts to someone other than the customers who own the hardware. Just over a dozen customers were caught up in it.

Luxor says it will reimburse those customers. That's the extent of what the company has put on the record so far.

How the rewards ended up elsewhere

The mechanism, as Luxor describes it, is a pool switch. Mining rigs constantly talk to whichever pool the operator has configured, and they report their work to that pool in exchange for payouts. Change the configuration and the machine keeps hashing, but the money goes somewhere else. In this case, that somewhere else was another pool under the attacker's control.

The affected miners wouldn't necessarily have noticed right away. A rig that's running and reporting shares looks healthy from the outside even when the payout address behind it has been swapped. The damage shows up in the wallet, not the dashboard.

A small blast radius

"Just over a dozen" is the number Luxor gave. On a platform with any meaningful customer base, that's a narrow slice, which suggests the hijack wasn't a broad compromise of the pool itself but something targeted at individual accounts or machines. Luxor hasn't said how the attacker got in, and it hasn't named the pool the machines were redirected to.

The company also hasn't detailed how it caught the redirect or how long the rewards were flowing to the wrong address before anyone noticed. Those are the questions that matter for every other customer wondering whether their own setup is clean.

Who eats the loss

Luxor has committed to reimbursing the affected customers, which puts the cost on the operator rather than on the miners. That's a reasonable call for a company the size of Luxor, and a cheap one given the headcount involved. A dozen-plus rigs redirecting for a limited window isn't a balance-sheet event.

But reimbursement settles the money, not the security question. Miners on any pool are trusting the operator's infrastructure with their payout routing, and a pool that can be induced to send rewards to a third party has a problem worth explaining. Luxor hasn't said whether the vulnerability was on its side or on the customers' machines, and that distinction matters a lot for everyone else.

What miners should watch

For now, the practical advice is the obvious one: check your payout address against what you configured, and don't assume a rig that's hashing is a rig that's earning. The customers whose machines were redirected found out the hard way that the two can come apart.

Luxor hasn't given a timeline for when the reimbursements will land or said whether it's pursuing the attacker. It also hasn't published what it changed to stop the redirect from happening again. Until it does, the question hanging over the incident is whether this was a one-off aimed at a handful of accounts or the first sign of something wider in how the pool handles machine configurations.