Hackers Hijack Bitcoin Miners Through Luxor's Commander Software, Redirecting Hashrate to OCEAN

Key Takeaways
- Luxor confirmed on November 15 that attackers redirected hashrate through its Commander fleet-management software, affecting just over a dozen client accounts.
- Luxor says it patched Commander within two hours, no data was leaked, Luxor Pool and LuxOS were unaffected, and every affected client will be paid in full.
- CoreX Hosting estimated about 64,000 machines and roughly 13 EH/s were pointed at the OCEAN pool; Luxor has not confirmed those figures.
- The attacker's address still received about 0.162 BTC from two OCEAN block payouts, sparking criticism from Luke Dashjr that the pool rewarded the hacker.
- CEO Nick Hansen blamed a "sophisticated AI-enabled vector," but Luxor has not yet published its promised post-mortem explaining how the attack worked.
Bitcoin miners woke up to an unusual kind of hack this weekend. Nobody's wallet was drained and no exchange went offline. Instead, someone quietly took control of mining machines and pointed their computing power at a pool of the attacker's choosing.
Luxor Technology, the bitcoin mining infrastructure company, confirmed on Sunday, November 15, that attackers carried out what it called "an unauthorized redirect of hashrate through Commander," its fleet-management software. The company says it patched the flaw within two hours and will pay affected clients in full.
Luxor CEO Nick Hansen went further, blaming "a sophisticated AI-enabled vector." That claim, plus a payout to the attacker that kept arriving after the hack was public, has turned a brief incident into one of the most talked-about stories in mining.
What happened over the weekend
The first alarm came from CoreX Hosting, a mining hosting firm, which warned on X that "there is a big miner hack going on as we speak." It said machines were being pointed at the OCEAN mining pool and paying out to a single bitcoin address, according to BeInCrypto.
Hansen later said the compromise began around 6 p.m. Pacific time on Saturday, November 14, when "a subset of Commander customers were compromised." In Luxor's words, "Last night our internal monitoring alerted us to an unauthorized redirect of hashrate through Commander. Our on-call engineering team jumped on it right away."
The company described the impact as "just over a dozen client accounts," with machines "pointed to a different pool for a limited window." It said no data was leaked or exfiltrated, and that Luxor Pool and its LuxOS firmware were not affected, as reported by The Block and Bitcoin.com News.
How big was it?
That depends on who you ask. CoreX put the damage at about 64,000 machines and roughly 13 exahashes per second (EH/s) of hashrate, BeInCrypto reported. OCEAN's own dashboard showed the attacker's address briefly nearing 14 EH/s before dropping back to almost zero.
If you are new to how mining power is measured, our explainer on hashrate covers what an exahash is and how it relates to mining difficulty.
Luxor has not confirmed either number. Its statement gives no machine count, no hashrate total and does not name the destination pool, AltcoinReporter noted. Bitcoin.com News also stressed that the 64,000-machine and 13 EH/s estimates remain independently unverified.
The attacker still got paid
Early reports suggested the hijacker walked away with nothing, because the redirected machines never found a block. That turned out to be wrong, and the reason lies in how OCEAN pays its miners.
OCEAN rewards miners for their recent work whenever the pool finds a block, even after they stop contributing. So when the pool later mined two blocks, the attacker's address was paid for shares submitted with the stolen hashrate. Galaxy head of research Alex Thorn tracked both payouts on-chain.
According to AltcoinReporter, the address received 0.08088977 BTC in block 975,995 and 0.08113106 BTC in block 976,029, for a total of about 0.162 BTC. BeInCrypto put that at more than $10,000. Mempool.space developer Mononaut had earlier estimated about 0.657 BTC in shares earned from the stolen hash, per OCEAN's dashboard, but that was a projection, not money received.
OCEAN faces criticism for not blocking the payouts
The payouts sparked a fight. Luke Dashjr, the longtime Bitcoin Knots developer who left OCEAN in August, accused the pool of rewarding the attacker. "OCEAN is profiting from a cyberattack on their own customers, and rewarding the attackers," he wrote, according to BeInCrypto.
Dashjr claimed the pool was set to send the attacker another $21,400 over the following 24 hours and would keep nearly $650 in fees. He argued OCEAN could simply have stopped telling its miners to reward the address once the news broke.
Not everyone agreed. One user argued that refusing to block the address shows Bitcoin's censorship resistance at work, adding that Luxor is making affected miners whole anyway. OCEAN had not publicly addressed the claims at the time of BeInCrypto's report. The debate echoes long-running arguments about filtering on the network, and about how much control mining pools should have.
The AI angle
Hansen's description of an AI-enabled attack is the part grabbing headlines, but the details are thin. Luxor has not published technical findings showing how the attackers got in, Bitcoin.com News reported, and AltcoinReporter pointed out that the "AI-enabled" wording comes from Hansen rather than the company's own statement.
Hansen framed it as part of a wider trend. "At this moment, anyone running any sort of substantial business, especially in crypto, is inundated with AI-enabled attacks," he wrote on X, as quoted by The Block. He said Luxor had acquired its own bare-metal GPUs to run its own models and had made "huge strides" in its security posture.
AltcoinReporter added that Hansen described an "AI-powered dark forest" and said Luxor had put most new feature work on hold to harden its infrastructure. Earlier this month, Binance also blamed part of its record breach on an internal AI tool and a fake job interview, a sign that AI is now a recurring theme in crypto security incidents.
Why it matters for miners
This was not a failure of the Bitcoin protocol, and no coins were stolen from Luxor's systems. What it shows is that the software used to manage large fleets can become a single point of failure. One compromised management tool was enough to point machines from more than a dozen client accounts at a pool their owners never chose.
For miners, that means lost revenue rather than lost coins, which is why Luxor's compensation promise matters. "Every affected client will be paid in full for the redirected hashrate, as if it had mined normally," the company said. Hansen also apologized: "You trust us with your fleet, and we need to be better."
The incident lands at a difficult moment. It comes just weeks after Luxor raised $16 million in a strategic round led by CMT Digital, with participation from Canaan, MicroBT and others, according to The Block. In September the company also announced Luxor AI, extending its business into AI and high-performance computing.
What comes next
Luxor has promised a full post-mortem but has not given a date. Until it lands, key questions remain open: exactly how attackers got into Commander, how long the redirect lasted, how compensation will be calculated and whether every machine is back on its original pool.
Hansen said affected clients would get an email with details, and early on Monday he replied that "the email should be out," AltcoinReporter reported. That is not the same as confirmation that payments have been made.
The OCEAN payouts should also wind down on their own once the attacker's shares fall out of the pool's reward window, which Thorn expected about a day and a half after the hijack. Whether the pool changes its rules for cases like this one is the bigger question the incident leaves behind.
DISCLAIMER
This article is for informational purposes only and does not constitute financial advice. Cryptocurrency investments involve substantial risk and extreme volatility - never invest money you cannot afford to lose completely. The author may hold positions in the cryptocurrencies mentioned, which could bias the presented information. Always conduct your own research and consider consulting a qualified financial advisor before making any investment decisions.









