0x2177101c2177…21771019

ConfirmedSecurity822 vB78 sat/vB4 min decode

Luxor Commander Breach Netted 0.162 BTC as Timeline Gaps Emerge

On-chain records show the address diverted through Luxor's Commander platform received two OCEAN coinbase payouts totaling 0.162 BTC, about $10,500 — a fraction of the hashrate's computed value.

Luxor Patched Commander in Two Hours. The Diverted Address Earned 0.162 BTC
WitnessLuxor Patched Commander in Two Hours. The Diverted Address Earned 0.162 BTCLauraTara / pixabay

Outputs

  1. Diverted address received two coinbase payouts totaling 0.16202083 BTC (~$10,512) on Nov. 15, both unspent.

  2. Luxor said it patched Commander within 2 hours and that just over a dozen client accounts were affected.

  3. Payout shares of ~2.59% imply roughly 1.04 EH/s credited, versus the 13 EH/s CoreX reported observing.

  4. At Nov. 16 prices, 13 EH/s equaled about $16,932 per hour in gross block reward.

  5. Luxor raised a $16 million strategic round led by CMT Digital.

An attacker who redirected bitcoin mining rigs through Luxor's Commander fleet-management platform collected 0.16202083 BTC, roughly $10,512, across two coinbase payouts on Nov. 15 — a fraction of the value of the hashrate CoreX reported diverted, according to on-chain records for the address Luxor's client published. Luxor confirmed the attack vector, the detection path and a two-hour patch window, but disclosed only one quantity: "just over a dozen client accounts" affected. The company gave no figures for machines, hashrate, lost hours or money. That silence is the story's center of gravity, because the compensation promise Luxor made is denominated in hashrate, and hashrate has a computable price.

What does the chain record actually show?

CoreX, the hosting operator that raised the alarm, published the diverted address — bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr — in its first alert. The address holds exactly two transactions, both coinbase outputs from blocks attributed to OCEAN's non-custodial pool.

  • Block 975,995 at 17:22:50 UTC on Nov. 15: 0.08088977 BTC
  • Block 976,029 at 22:54:00 UTC on Nov. 15: 0.08113106 BTC
  • Neither output has been spent; balance stands at 0.16202083 BTC

The second payment landed roughly five and a half hours after Luxor said Commander was patched and restoration had begun. CoreX's own posts complicate the vendor timeline. At 03:57 UTC on Nov. 15, the host wrote that "the attack is on-going, the hacker pool address is still sitting at 13EH" and added: "I am changing miners back as I can." A patched control plane and a restored fleet are separate clocks, and Luxor's "no action is needed from users" reads differently against an operator reversing settings machine group by machine group.

Why does 2.6% matter more than 13 EH/s?

The two payouts are nearly identical in size, and in OCEAN's TIDES system the payout share is a direct statement of credited work. The first payment equals 2.583% of its block's outputs; the second equals 2.589%. Against OCEAN's reported 40.35 EH/s, that implies roughly 1.04 EH/s of credited work — about one-thirteenth of the 13 EH/s CoreX observed. Two explanations fit, and they are not exclusive: machines may have been pointed at the endpoint without submitting valid shares, or the 13 EH/s reading captured a transient peak. OCEAN has published no notice about the event, though its sharelog for the two blocks would settle the question in a single query. Until someone publishes it, the gap remains a measured discrepancy, not a proven overstatement.

OCEAN's TIDES design explains only part of the residual. TIDES pools rewards across an eight-block difficulty window — roughly 31 hours of pool history at 40 EH/s against a 934 EH/s network — which can dilute a late joiner's first payout. But by 22:54 UTC the diverted address had been in the window for most of a day; a sustained 13 EH/s would have earned a share in the tens of percent, not 2.6%. The chain reads like a mostly contained incident with a small residue.

What does "paid in full" cost?

Luxor promised compensation in full, priced in hashrate. At the Nov. 16 difficulty and the $64,883 bitcoin price recorded by CoinGecko, 13 EH/s on a 934 EH/s network would earn about $406,373 a day in gross block reward — $16,932 an hour before fees and power. Two hours of redirection costs $33,864; the 15.4 hours to Luxor's statement costs $261,038; the 20.9 hours to the last observed payout costs $353,883. Luxor raised a $16 million strategic round led by CMT Digital, so none of these figures threatens the company. The exposure is reputational, and the precedent is the real cost: a software vendor has accepted revenue liability for hashrate it does not own.

The control plane, not the Bitcoin protocol, was the attack surface. No consensus rule broke and no double spend occurred; a configuration value on machines owned by others changed through software built for bulk convenience. CoreX wrote "pretty sure I have isolated what I think is the program used," pointing toward client-side compromise rather than a breach of Luxor's platform — a distinction that remains publicly unresolved, despite the vendor's SOC 1 examination and SOC 2 compliance, which cover only Luxor's internal controls.

The pending post-mortem Luxor committed to is the only document that can close the gap. It should disclose the machine count and redirected hashrate, the UTC start and end of the redirection, and the compensation math. Operators' practical lesson is narrow: verify pool endpoints and payout addresses on the machines, not in the dashboard. The attacker captured roughly 3% of what the diverted hashrate was worth, apparently due to timing rather than restraint. The next attempt may land better.

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,525 articles