0x401b0216401b…401b0213

ConfirmedSecurity535 vB48 sat/vB3 min decode

Luxor Pledges Full Compensation After Commander Hijack Redirected Mining Fleets

Luxor CEO Nick Hansen pledged full compensation after Commander was used to redirect client fleets, with CoreX reporting 13 EH/s hijacked to a single OCEAN address.

Luxor Pledges Full Compensation for Commander Hijack
WitnessLuxor Pledges Full Compensation for Commander Hijackrebcenter-moscow / pixabay

Outputs

  1. Luxor CEO Nick Hansen pledged full compensation for the Commander hijack and promised a full post-mortem.

  2. CoreX Hosting reported about 13 EH/s redirected to a single OCEAN address, later falling to about 100 PH/s.

  3. The flagged OCEAN address received a payout of roughly 0.0809 BTC despite finding zero blocks.

  4. Luxor says the issue was isolated to Commander and that no data was leaked or exfiltrated.

Mining-software firm Luxor has pledged full compensation to clients affected by a hijack of its Commander fleet-management platform, Chief Executive Officer Nick Hansen announced. In a public statement, Hansen said affected clients would receive an email the same day with details of the remedy. "You trust us with your fleet, and we need to be better," he wrote.

The admission is notable for what it concedes: Commander was the route through which affected mining fleets were redirected, presumably toward an attacker-controlled pool configuration. What Luxor has not yet explained is the underlying exploit itself. The company has not described how the redirection was executed, how long it persisted, or how many client fleets were exposed. A full post-mortem has been promised, though no timeline accompanied that commitment.

What does Luxor say was affected?

Luxor states the issue was isolated to Commander, and that its other products, including the Luxor Pool and the LuxOS firmware layer, were unaffected. The company also says no data was leaked or exfiltrated from its systems. That is a narrower claim than it may first appear: it addresses data confidentiality, not the operational integrity of mining redirection, which is the core of the incident.

Commander is not merely a monitoring dashboard. Luxor's own product page describes the software's capacity to change pool settings across thousands of miners in a single bulk operation. That authority is precisely what makes the platform efficient at scale, and precisely what made it a powerful vector when misused. An attacker holding the management layer does not need to touch individual machines to redirect their work.

What did the redirection cost in hashrate?

Mining host CoreX Hosting, one of the affected operators, reported roughly 13 exahashes per second (EH/s) at the address it identified with the attack, while it worked to point its miners back to legitimate destinations. That figure is substantial: 13 EH/s represents a meaningful share of the Bitcoin network's total hashrate, which trades in the low hundreds of exahashes. CoreX later said the flagged address's hashrate had collapsed to about 100 petahashes per second — a fall of more than 99 percent, indicating the redirection had largely been unwound.

The OCEAN pool dashboard for that address records zero blocks found. It also records a payout of approximately 0.0809 BTC, and the corresponding on-chain transaction confirms that amount reached the address CoreX flagged.

These figures are not contradictory. Under OCEAN's TIDES reward system, miners earn a proportional share of rewards for work recorded within the pool's reward window whenever any pool participant finds a block. An address therefore need not find a block itself to receive payment. Equally, that single payout is not a measure of total lost revenue across all affected clients; losses would accrue as redirected work, not only as collected rewards.

What happens next?

Luxor says Commander is now operating normally and that users need to take no action. The company has promised a full post-mortem, but has not set a date, quantified total client losses, or specified the form compensation will take. Until that document arrives, the central question — how the management layer was compromised — remains unanswered.

via cryptonews.net (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

1,213 articles