Incident facts
| Affected party | Luxor Commander |
|---|---|
| Event date | November 15, 2026 |
| Network | Bitcoin |
| Status reported by source | Attack contained |
| Estimated loss | Amount under review |
| Frozen | No confirmed data |
| Returned | No confirmed data |
What happened
Luxor says attackers used Commander to redirect mining hashrate from just over a dozen customer accounts during the night of 14–15 November. The company reports patching the software within two hours and restoring pool settings.
Luxor says the incident was limited to Commander, with Luxor Pool and LuxOS unaffected. It promises full compensation for redirected mining revenue; completed payments and aggregate losses have not been disclosed. Reported payouts to one address do not establish the total loss.
Total lost mining revenue remains unconfirmed. The compensation promise is not recorded as funds already returned.
Sources
- Luxor — Commander incident statement — Original source · x.com · November 15, 2026
- Luxor statement — public archive — Report · teapaw.org · November 15, 2026
- Coindaro — incident and payout review — Report · www.coindaro.com · November 16, 2026
Information is attributed to the linked sources and has not been independently verified by Match Systems. Loss estimates and incident status may change as new evidence becomes available.
Latest incidents
- Key compromiseLighter DEX Halts Withdrawals After $10.4M USDC Stolen via Leaked Trader API Key
- ExploitRujira: funds traced to Ethereum as restart awaits audit
- Key compromiseUnocoin estimates $200K loss after backup-key compromise
- ExploitPool Party: 15 pools drained through a position-recording flaw
- ExploitKava Lend: collateral accounting flaw linked to $3.7M loss
- ExploitCertiK clarifies the UTC date and valuation limits