Daily news

Luxor Confirms Commander Breach Behind Bitcoin Hashrate Hijack, Blames 'AI-Enabled' Attack and Pledges Full Compensation

Luxor says an unauthorized hashrate redirect through its Commander fleet-management tool affected just over a dozen client accounts, was patched within two hours and will be fully compensated. CEO Nick Hansen blamed a “sophisticated AI-enabled vector,” but the entry point remains undisclosed. On-chain data shows OCEAN paid 0.162 BTC to an attacker-linked address.

MyTraderBot DeskPublished: 11 min readخواندن به فارسی
Share
Rows of cryptocurrency mining machines on blue metal shelves in a mining farm hall, with MyTraderBot branding in the corner
Cryptocurrency mining farm (file photo). Photo: Marco Krohn, CC BY-SA 4.0, via Wikimedia Commons
Table of Contents

Luxor Technology has confirmed that its Commander fleet-management software was used to redirect bitcoin mining hashrate away from client machines on the night of November 14–15, 2026, the incident that sent mining power to the OCEAN pool and a single attacker-linked payout address. Luxor says "just over a dozen client accounts" were affected, Commander was patched within two hours, no data left its systems, and every affected client will be paid in full for the redirected hashrate. CEO Nick Hansen blamed "a sophisticated AI-enabled vector," but neither he nor the company has yet explained how the attacker got in.

When we first reported the hijack on November 15, the Commander link rested on a single operator's claim and Luxor had said nothing. That part of the story is now settled. Other parts, including the reported 64,000 machines and 13 EH/s, are still not confirmed by Luxor. This update separates confirmed facts, company statements, third-party claims and our own analysis.

What is new since our first report

  • Luxor confirmed the Commander link. In an official post on X at 17:25 UTC on November 15 (20:55 Tehran), Luxor said its internal monitoring "alerted us to an unauthorized redirect of hashrate through Commander."

  • Luxor says the breach was limited to Commander. In a follow-up post it said the issue "was isolated to the Commander tool" and that "None of Luxor's other services (including Luxor Pool and LuxOS) were affected."

  • Full compensation was promised. "Every affected client will be paid in full for the redirected hashrate, as if it had mined normally," the company wrote.

  • The CEO described the method as AI-enabled. Hansen's posts called it "a sophisticated AI-enabled vector" and warned of an "AI-powered dark forest."

  • The attacker's address has now been paid. On-chain data shows two OCEAN block-reward payouts to the address that hosting company CoreX flagged, totalling 0.16202083 BTC. Our first report noted that no payout had been made yet.

What Luxor said, in its own words

The company statement

Luxor's post said its on-call engineering team "jumped on it right away." On impact, it wrote: "just over a dozen client accounts. Affected machines were pointed to a different pool for a limited window. No data was leaked or exfiltrated from our systems." On the response: "within 2 hours Commander was patched and we started restoring affected machines to their original pool settings." It added that Commander "is operating normally and no action is needed from users," and that it is "working with the teams involved and will share a full post-mortem."

The CEO's account

About eight minutes earlier, at 17:17 UTC (20:47 Tehran), Hansen wrote on X: "The last 12 hours have been pretty rough. Around 6:00p PDT yesterday, a subset of Commander customers were compromised, through a sophisticated AI-enabled vector." He said affected clients "will receive an email today with more details," and added: "I apologize. You trust us with your fleet, and we need to be better."

A note on timing: Hansen wrote "PDT," but US daylight saving time ended on November 1, so the US West Coast was on PST (UTC−8). "6 p.m. Pacific on November 14" therefore works out to about 02:00 UTC on November 15 (05:30 Tehran) if he meant local time, or 01:00 UTC (04:30 Tehran) if he literally meant PDT. Earlier media reports put the start at around 02:00 UTC. We treat the exact start as approximate.

The "dark forest" warning

In a second, longer post at 18:04 UTC (21:34 Tehran), which Luxor's account quoted, Hansen wrote: "At this moment, anyone running any sort of substantial business, especially in crypto, is inundated with AI-enabled attacks." He added: "Abliterated models are running 24/7 against your entire surface, looking for a little crack, which they then use to (almost instantly) expand," and "This does not seem to be slowing down; rather, it's speeding up as models get better and more attackers enter the arena."

Hansen said Luxor has acquired its own bare-metal GPUs to run its own abliterated models, and urged similar services to do the same: "It's your only defense in this new AI-powered dark forest." He also said the company has put most new feature work on hold to harden its infrastructure: rotating keys, updating kernels, pinning dependencies and responding to the daily feed of new CVEs (publicly catalogued software vulnerabilities).

Confirmed vs. unverified

Claim

Status

Hashrate was redirected through Luxor Commander

Confirmed by Luxor

"Just over a dozen client accounts" affected

Luxor's statement; not independently verified

No data leaked or exfiltrated; Luxor Pool and LuxOS unaffected

Luxor's statement; not independently verified

Patched within two hours; full compensation

Luxor's statement and pledge

About 64,000 machines and about 13 EH/s redirected

Third-party claim (CoreX Hosting, media); not confirmed by Luxor

Attack was "AI-enabled"

CEO's description; no technical evidence published

Technical entry point

Not disclosed; post-mortem pending

Attacker address received 0.16202083 BTC

Verified on-chain

"Just over a dozen client accounts" does not contradict the larger figures. A single Commander account can control a whole hosting site or farm, so a dozen accounts could cover tens of thousands of machines, or far fewer. Luxor has given neither a machine count nor a hashrate figure. Cointelegraph also noted that Luxor has not confirmed the 64,000-machine and 13 EH/s numbers.

Timeline (UTC and Tehran)

Event

UTC

Tehran (UTC+3:30)

Attack begins ("around 6 p.m. Pacific," Nov. 14; approximate)

Nov. 15, ~01:00–02:00

Nov. 15, ~04:30–05:30

CoreX Hosting posts first public alert

Nov. 15, 03:08

Nov. 15, 06:38

CoreX says "It is over"

Nov. 15, 06:40

Nov. 15, 10:10

Hansen confirms compromise on X

Nov. 15, 17:17

Nov. 15, 20:47

OCEAN block 975,995 pays 0.08088977 BTC to the address

Nov. 15, 17:22

Nov. 15, 20:52

Luxor official statement

Nov. 15, 17:25

Nov. 15, 20:55

Luxor: issue isolated to Commander

Nov. 15, 17:32

Nov. 15, 21:02

Hansen "dark forest" post

Nov. 15, 18:04

Nov. 15, 21:34

OCEAN block 976,029 pays 0.08113106 BTC to the address

Nov. 15, 22:54

Nov. 16, 02:24

MyTraderBot on-chain check: both outputs unspent

Nov. 16, 05:39

Nov. 16, 09:09

The on-chain payouts

The address CoreX flagged, bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr, received two coinbase outputs, meaning payments created directly in the reward transaction of a newly mined block:

  • 0.08088977 BTC in block 975,995 (block time 17:22:50 UTC, Nov. 15)

  • 0.08113106 BTC in block 976,029 (block time 22:54:00 UTC, Nov. 15)

The total is 0.16202083 BTC. According to mempool.space, both outputs were still unspent when we checked at 05:39 UTC on November 16 (09:09 Tehran). At Coinbase's BTC spot price of about $64,683 at that moment (Coinbase public API), that is roughly $10,480.

On November 15, OCEAN's dashboard estimated about 0.658 BTC of rewards for this address's shares in its reward window. That was an estimate, not a promise; the actual amount depends on when OCEAN finds blocks and on how long the shares stay in the window.

Please do not send funds to or interact with this address. It is listed so operators can recognize it.

Why the pool cannot simply claw this back

Most large pools collect block rewards themselves and pay miners later from their own wallets, so they can, in principle, hold back a suspicious payout. OCEAN works differently. Its TIDES system (Transparent Index of Distinct Extended Shares) credits miners for their recent shares, and payouts above a threshold are written straight into the coinbase transaction of each block OCEAN finds. Once that block is confirmed, the bitcoin sits in the miner's own address. The pool never holds it, so there is nothing to freeze.

Because TIDES counts a rolling window of recent shares, shares submitted during the hijack can be credited across more than one block. That is consistent with the two payouts above. OCEAN has not said publicly whether it will exclude these shares from future blocks.

What Commander is and why it matters

Commander is Luxor's fleet-management tool. Large miners and hosting companies use software like it to monitor thousands of ASIC machines, update firmware, tune performance and change pool settings in bulk from one dashboard.

That convenience is also the risk. Every bitcoin miner is configured with a pool address and a worker name that determine who gets paid. If an attacker controls the software that can rewrite those settings for whole fleets, they do not need to touch each machine. One compromised control plane becomes a single point of failure.

Hashrate redirection means exactly that: the machines keep running and burning electricity, but their work is submitted to a pool and payout address chosen by the attacker. The owner pays the power bill; someone else collects the rewards. Bitcoin itself was not hacked. The protocol and blockchain worked as designed.

What is an "abliterated" model?

"Abliteration" is a technique used on open-weight AI language models to remove their built-in refusal behavior, so the model no longer declines harmful requests such as writing exploit code. Hansen's argument is that attackers run such models nonstop to scan for weaknesses, and that defenders must use similar tools to find the same flaws first. He did not say how AI was used in this attack, and Luxor has not described the entry point.

Industry context

Luxor is not the only firm pointing to AI. Cointelegraph reported on other recent warnings about AI-assisted intrusions, including an India CERT alert about a campaign dubbed "Crafty Falcon," a Chainalysis disclosure in October about "offensive agentic techniques," and an Anthropic report in September on "automated exploit foundries." These are Cointelegraph's summaries; we have not reviewed those reports ourselves.

The breach also fits a wider pattern of crypto incidents that start in supporting software rather than in blockchains: a support contractor in the Coinone data leak, logging tools in the Proxima wallet drain, and public code in the BitGo frontrunning claims.

According to The Block, Luxor raised $16 million last month in a strategic round led by CMT Digital, with Canaan, MicroBT, Halo and Steelhead participating, and in September announced Luxor AI, a high-performance computing and AI unit.

What it means for miners

  • If you use Commander, Luxor says no action is needed. It is still sensible to check that each machine's pool URL, worker name and payout address match your records.

  • Watch for Luxor's email on compensation and keep your own hashrate logs to check the amount.

  • For any fleet tool, limit who can change pool settings, use two-factor authentication, rotate API keys and keep management interfaces off the public internet.

  • Set alerts for sudden hashrate drops at your pool; that is often the first sign of redirection.

Mining margins are already under pressure; see our report on November's 9% difficulty drop and hashprice. A few hours of lost output matters, which is why the compensation pledge is significant for affected clients.

What it means for traders

This was an operational security incident at a mining-software provider, not a flaw in Bitcoin. The amounts paid to the attacker so far are small relative to daily network rewards, and the reported 13 EH/s was about 1.4% of network hashrate, far from any threat to consensus. The more lasting point is about risk in crypto infrastructure: third-party tools remain a frequent entry point, and companies are increasingly citing AI-assisted attacks. This article contains no price forecast or trading signal.

What to watch

  • Luxor's promised post-mortem, which should explain the entry point and what "AI-enabled" means here. As of 05:39 UTC on November 16 we found none published.

  • Whether Luxor confirms or corrects the 64,000-machine and 13 EH/s figures.

  • Whether OCEAN makes further payouts to the address or excludes its shares.

  • Whether the 0.162 BTC is moved, which could allow it to be traced.

  • Whether other fleet-management vendors report similar attempts.

FAQ

Did Luxor confirm Commander was the cause?

Yes. Luxor said its monitoring detected "an unauthorized redirect of hashrate through Commander" and that the issue was isolated to that tool.

Were Luxor Pool or LuxOS affected?

Luxor says no. It stated that none of its other services, including Luxor Pool and LuxOS, were affected. This has not been independently verified.

Will affected miners be compensated?

Luxor says every affected client will be paid in full for the redirected hashrate, as if it had mined normally, with details sent by email.

How much did the attacker receive?

On-chain data shows 0.16202083 BTC paid to the flagged address in two OCEAN blocks, unspent as of our check. Further payouts are possible.

How was AI used in the attack?

Not disclosed. Hansen called the vector "sophisticated" and "AI-enabled," but Luxor has not published technical details.

This article is news reporting, not investment advice. Details may change when Luxor publishes its post-mortem.

Sources

Coins mentioned
  • BTCBitcoin
Share

See the signals and their results

Browse publicly logged signals and how they performed, or create a free account to follow them.

Luxor Confirms Commander Breach Behind Bitcoin Hashrate Hij…