Hackers Hijack Luxor Commander and Redirect Miners' Hashrate to OCEAN
Security

Hackers Hijack Luxor Commander and Redirect Miners' Hashrate to OCEAN

November 16, 20264 min read

Attackers broke into Commander, Luxor's tool for managing mining hardware, and over the weekend redirected customers' computing power to another pool. For miners this is an especially nasty scenario, because nothing is withdrawn from a wallet. The earnings themselves get intercepted.

What exactly happened at Luxor?

Luxor sells miners a pool and software. Commander is the dashboard where customers control their machines and, among other things, set which pool they connect to. On Saturday attackers changed those settings for Luxor customers. According to early reports, about 64,000 machines with a combined 13 exahashes per second ended up in the OCEAN pool. Luxor has not confirmed those figures and says just over a dozen customer accounts were affected.

In short: through a compromised Commander, hackers swapped the pool that customers' machines work for, so their hashrate went to a stranger's address.

The company says it patched Commander within two hours of spotting the unauthorized changes and started restoring the machines' original settings. Its other services, Luxor Pool and LuxOS, were not hit, according to Luxor. Customers are promised full compensation for the redirected power and a public post-mortem.

Why do miners use pools, and why is a swap so painful?

A lone miner rarely finds a block alone, because the Bitcoin network is huge and one machine's odds are tiny. So miners join pools. A pool gathers the power of many participants, searches for blocks together and splits the reward in proportion to each contribution. Payouts arrive regularly, in small pieces.

That setup is why a pool swap hurts. The machine keeps humming, burning electricity and showing a healthy hashrate. Nothing changed for the device itself. But the contribution is now counted somewhere else, for someone else. Owners rarely check the chosen pool every day, and this kind of attack counts on exactly that.

How does hashrate redirection work?

To see why this worked, it helps to recall how a miner gets paid at all. The machine decides nothing on its own. It takes a task from the pool, tries hash variations and returns the result. Where it sends the work depends on the pool address in its settings. Who gets paid depends on the account the machine uses in that pool.

  • Pool address: a line in the settings that tells the device whom to hand its hashes to.
  • The pool account is tied to a payout address, so the reward goes to whoever's account is set.
  • A bulk management tool like Commander changes these fields for hundreds or thousands of machines at once.
  • The owner notices the problem when payouts stop and a stranger's name shows up on the dashboard.

That is why this kind of attack is dangerous. It needs no physical access and no break-in to each device, just one way into the panel that runs the whole fleet. Until someone notices the change, a foreign pool gets work that the customer paid for with electricity.

Did the attackers get paid?

At first reports said they received no rewards. Then the picture changed. A Bitcoin address that analysts at CoreX linked to the incident received two payouts from OCEAN totaling about 0.162 BTC. That is roughly $10,500.

For an attack of this size it is not much. Luxor has not fully confirmed how much power ran for the other pool or for how long, so the customers' losses cannot be counted yet. The company promises details in its post-mortem. If you wonder what that is in money, we show live prices for how to exchange Bitcoin for dollars.

Why is Luxor talking about AI?

Luxor CEO Nick Hansen wrote on X on Sunday that the attack came through a "sophisticated AI-enabled vector". He did not say how AI was used. His main point is that such attacks will only multiply.

"At this moment, anyone running any sort of substantial business, especially in crypto, is inundated with AI-enabled attacks. This does not seem to be slowing down; rather, it's speeding up as models get better and more attackers enter the arena."

- Nick Hansen, Luxor CEO, from an X post of November 15, 2026

Hansen described Luxor's own defense like this. The company shelved most feature work to harden security and bought its own GPUs to run unrestricted open-weight models and find its own weak spots first. He urges similar services to do the same. That is the company's position, and there is no independent confirmation yet that AI really played a part in the attack.

There is context behind his warning, though. Earlier this month India's cybersecurity agency warned that a group called Crafty Falcon uses AI tools against financial firms and crypto exchanges and steals wallet keys. In October Chainalysis admitted an attacker got into its systems with "offensive agentic techniques", exposing password hashes and live tokens. And Anthropic wrote in a September report about "automated exploit foundries" that several groups built with AI.

What should miners do after this?

The lesson is down to earth. A control panel for a fleet of machines is as critical as a wallet with keys. Anyone who mines Bitcoin through cloud services should turn on two-factor login, limit who has access and set alerts for any change of pool or payout address.

One more simple habit: once a day, check where the hashrate actually goes and whether payouts match expectations. A pool swap shows up only when someone looks at the numbers.

Share:

Comments

Your email address will not be published. Required fields are marked *

or verify by email