Luxor Technology disclosed that an intrusion briefly redirected hashrate from some clients of its Commander fleet-management software to the OCEAN mining pool on November 14, 2026. The company says the flaw was patched within two hours and that no data left its systems, but the scale of the incident remains unverified, and the AI-enabled attack label rests so far on its CEO’s statements alone.
๐ Key takeaways
- Roughly two hours of client hashrate were pointed at the OCEAN pool, according to Luxor and CoreX Hosting.
- Luxor says “a little more than a dozen” client accounts were affected; social media posts cited about 64,000 machines, which remain unconfirmed.
- OCEAN’s dashboard shows 0.657 BTC in estimated shares, while about 0.162 BTC in payments has been observed, roughly $10,500 at the time.
- CoreX cited about 13 EH/s of hashrate tied to the attacker address; Luxor has not confirmed this figure.
- The “AI-enabled attack” label comes from CEO Nick Hansen, with no technical analysis published yet.
A two-hour redirection through Commander
According to CEO Nick Hansen, the compromise began around 6:00 p.m. Pacific time on Saturday, November 14. Luxor confirmed the incident on Sunday, November 15, saying its internal monitoring had detected unauthorized hashrate redirection through Commander. Its on-call team moved in immediately, patched the vulnerability within two hours, and began restoring machines to their original pool configurations.
Commander is fleet-management software that lets operators monitor and reconfigure thousands of miners from a single interface. The product’s own site says it can change pool settings across thousands of machines in one operation. Compromising that management layer was therefore enough to change where miners sent their work, without touching each device individually.
The destination pool, OCEAN, is a non-custodial Bitcoin mining pool launched in 2023 with financial backing from Jack Dorsey. Miners are paid directly through the coinbase transactions (the transaction that carries a block’s reward) of the blocks they help find. The incident was first flagged by CoreX Hosting, a mining infrastructure operator that found unauthorized pool settings on its machines. CoreX said it began returning its miners to normal configuration and confirmed the problem was resolved the following day.
Luxor says no other services were reached and no data was disclosed or exfiltrated from its systems. Its statement describes “a little more than a dozen client accounts” and notes that affected machines were pointed at another pool for a limited window.

Numbers that do not yet add up
Luxor has confirmed neither the number of affected machines nor the hashrate actually diverted. Estimates shifted over the hours, and several metrics measure different things. The table below lists each figure with its verification status.
| Metric | Value | Source | Status |
|---|---|---|---|
| Clients affected | “a little more than a dozen” | Luxor | Stated, not quantified |
| Machines reported | about 64,000 | Social media | Unconfirmed |
| Diverted hashrate | about 13 EH/s, then about 100 PH/s | CoreX Hosting | Not confirmed by Luxor |
| Total OCEAN hashrate | near 50 EH/s | Crypto Briefing | Peak observed |
| Estimated shares | 0.65761026 BTC | OCEAN dashboard | Estimate |
| Address payout | 0.0809 BTC | OCEAN dashboard | Confirmed on-chain transfer |
| Observed payments | about 0.162 BTC (about $10,500) | Recent report | Payments observed |
The figure of 0.657 BTC refers to estimated reward shares on OCEAN’s dashboard. Developer Mononaut commented on the number:
“Oh, about 0.657 BTC in shares won from the stolen hashrate, according to OCEAN’s dashboard.”
Mononaut, developer
Early blockchain records showed no confirmed incoming transactions to that address, suggesting the accumulated rewards had not yet been paid out. Later, OCEAN’s dashboard for the address flagged by CoreX showed zero blocks found but a payout of about 0.0809 BTC. A matching on-chain transaction confirmed that amount was transferred to the address. More recent information points to two payments from OCEAN totaling about 0.162 BTC, or roughly $10,500 at the time of the incident.
The 0.657 BTC and 0.162 BTC figures therefore measure different things: one is an estimate of reward shares, the other a set of payments actually observed. Neither captures the full revenue lost by affected clients. A missing block find does not rule out a payment either. Under OCEAN’s TIDES system, a miner can receive a proportional share of rewards when another pool participant finds a block, provided its work was recorded during the calculation window. No block, however, was mined with the diverted hashrate. CoreX, OCEAN and Luxor have not publicly linked these observations into a single technical chain beyond the redirection to OCEAN.
Limited consensus impact, real costs for miners
According to Crypto Briefing, the 13 EH/s estimated by the community would represent about 1.4% of total Bitcoin network hashrate at the time. The outlet judged that this share, held for a very short period, was insufficient to threaten Bitcoin’s consensus. OCEAN’s total hashrate briefly reached near 50 EH/s during the affected window.
Who bore the costs
- Miners kept running and continued paying their electricity bills.
- Part of their rewards was credited to an address associated with OCEAN, which is the main documented consequence: the destination of payouts.
- Luxor has published no aggregate loss figure. It says each affected client will be “fully paid for the redirected hashrate, as if they had mined normally.”
- A follow-up email to affected clients was expected on November 15.
- The Block asked Luxor for more detail and received no further response. OCEAN has not commented publicly, and no source reports a Bitcoin price move attributable to the breach.
An AI-enabled attack not yet demonstrated
The AI-enabled classification currently rests on Nick Hansen’s statements. Luxor has not yet published a technical analysis showing how attackers obtained the permissions needed to change pool configurations, or what role AI played in the exploitation chain. Hansen has broadened the warning to the whole sector:
“Right now, anyone running a substantial business, especially in crypto, is being overwhelmed by AI-enabled attacks.”
Nick Hansen, CEO, Luxor Technology
Hansen argues the trend is not slowing: attacks are accelerating as models improve and more attackers enter the field. He describes the threat this way:
“Unshackled models run 24 hours a day against your entire attack surface, looking for a small crack they then use to expand almost instantly.”
Nick Hansen, CEO, Luxor Technology
In response, Luxor says it bought its own GPUs to run unrestricted models and is devoting more resources to hardening its defenses. BigGo Finance reports that the company has suspended much of its new feature development to focus on that work. Luxor has also apologized to clients. Hansen wrote: “I am sorry. You trust us with your fleet, and we have to do better.”
A wider threat backdrop and Luxor’s AI push
Luxor Technology is a Bitcoin mining infrastructure company that combines a mining pool, ASIC firmware, miner-management software, hardware and energy services. In September 2026 it announced Luxor AI, extending its mining infrastructure toward artificial intelligence and high-performance computing. In October it raised $16 million in a strategic round led by CMT Digital, with Canaan, MicroBT, Halo and Steelhead among the participants. No source links that funding or the Luxor AI project to the breach.
BigGo Finance places the incident within a series of AI-assisted intrusions. India’s cybersecurity agency warned this month that the group Crafty Falcon was using AI-powered tools against financial institutions, including crypto platforms, to steal wallet keys and drain funds. In October, Chainalysis disclosed that an attacker used what it called “agentic offensive techniques” to reach its systems, exposing password hashes and active tokens. In a September threat intelligence report, Anthropic noted that several groups had built “automated exploitation factories” with AI, shortening the time between discovering a flaw and weaponizing it. No published material shows these actors are linked to the Luxor attack.
Outlook and scenarios
Several questions remain for the post-mortem Luxor has announced: the exact access path into Commander, the real number of affected machines, the total hashrate diverted, and how thoroughly machines were verified after restoration. Until those points are published, the available figures should be read with caution.
Three scenarios stand out. In the base case, technical analysis confirms a limited incident affecting a small number of accounts, with no effect on consensus and a financial impact confined to the payments already identified. In a less favorable case, the investigation reveals broader access to the management layer, with more machines or clients involved. A third, more structural scenario sees this type of attack multiply against fleet-management software, which would push the sector to tighten access controls and monitor pool settings more closely.
Sources
- The Block, November 15, 2026
- CryptoNews, mining
- Bitcoin.com News, security
- Crypto Briefing, Luxor CEO statements
- BigGo Finance
- TradingView (Crypto Briefing repost)
Cet article est publiรฉ ร titre informatif et รฉducatif. Il ne constitue en aucun cas un conseil en investissement. Faites vos propres recherches (DYOR) avant toute dรฉcision.


