Luxor Technology said on 15 November that an unauthorised redirect of hashrate through its Commander fleet-management tool had pointed affected machines at a different mining pool. In a post on X at 17:25 GMT, the company said internal monitoring had alerted it “last night,” that the impact covered “just over a dozen client accounts,” and that “no data was leaked or exfiltrated from our systems.”
A follow-up seven minutes later said the issue “was isolated to the Commander tool” and that “none of Luxor’s other services (including Luxor Pool and LuxOS) were affected.” Luxor said that within two hours Commander had been patched and that it had started restoring affected machines to their original pool settings. “Every affected client will be paid in full for the redirected hashrate, as if it had mined normally,” the company said. Commander was “operating normally and no action is needed from users.” A full post-mortem was promised.
Hansen put the start at 6:00 p.m. PDT on 14 November
Nick Hansen, Luxor’s chief executive, posting as @hash_bender at 17:17 GMT, wrote that “around 6:00p PDT yesterday, a subset of Commander customers were compromised, through a sophisticated AI-enabled vector.” On a 15 November post, that timing is 6:00 p.m. PDT on 14 November, or 02:00 GMT on 15 November. Hansen said Luxor “will fully compensate clients that were affected” and that they would “receive an email today with more details.” He apologised, said Commander was operating normally, and added that “no further action is needed.”
He did not describe how the vector worked, or how access to Commander was gained. Those points are still unstated in the official posts.
In a later thread at 18:04 GMT, which Luxor quoted, Hansen said that “anyone running any sort of substantial business, especially in crypto, is inundated with AI-enabled attacks.” He wrote that “abliterated models are running 24/7” against a firm’s surface. He said Luxor had “acquired our own baremetal GPUs to run our own abliterated models,” and that it had “put the majority of our new feature work on hold” to “harden every aspect of our infrastructure; rotating keys, updating kernels, pinning dependencies and responding to the daily feed of CVEs being disclosed.” The thread is a description of the pressure he says the company has been under. It is not an account of the Commander redirect itself.
A hosting firm flagged a destination earlier that morning
Hours before Luxor’s confirmation, CoreX Hosting posted at 03:08 GMT on 15 November that “there is a big miner hack going on as we speak” and that miners were “being pointed at @ocean_mining with BTC address bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr.” That destination and address come from CoreX, not from Luxor. OCEAN has not published a statement in the sources reviewed for this report.
CoinDesk, in a 16 November article by Shaurya Malwa, reported that the address flagged by CoreX had since received three bitcoin block-reward payments totalling about 0.243 BTC, worth roughly $15,700, and that none of those coins had been spent as of Monday morning. CoinDesk also wrote that OCEAN payout rules can let earlier work keep earning for a rolling period. Those on-chain figures and the payout explanation are CoinDesk’s reporting, not Luxor’s. The Block, in a 15 November report by Timmy Shen, likewise covered the Commander incident and noted Luxor’s $16 million raise last month, which TSN has already recorded.
The incident sits in the same industry as other pool-side changes, including Binance’s planned shutdown of Binance Pool, and it sits beside other crypto security incidents TSN has covered, including the Binance hack in which withdrawals later reopened in phases. Those are neighbouring stories, not the same event.
A redirected machine is not a theft from a client wallet
The official record, as it stands on 16 November, is narrow. Luxor has confirmed an unauthorised redirect of hashrate through Commander, limited to just over a dozen client accounts, isolated from Luxor Pool and LuxOS, with no data leaked or exfiltrated from its systems, and with a promise to pay every affected client as if the machines had mined normally. Hansen has given a start time and has called the vector “sophisticated” and “AI-enabled.” He has not said what that vector was.
That gap matters. A claim that an attack was AI-enabled is not a description of how Commander was reached, which accounts were touched first, or how long the “limited window” lasted beyond Luxor’s statement that the tool was patched within two hours. Filling those blanks from Hansen’s later remarks about abliterated models and bare-metal GPUs would be speculation. Those remarks are about a wider climate he says the company has faced for weeks. They are not a post-mortem of this incident.
The same caution applies to the coins. Redirecting a miner to another pool means the work of those machines was pointed somewhere else for a period. It is not, on the official record, a finding that bitcoin was taken from client wallets. Luxor’s remedy is compensation for the redirected hashrate. CoinDesk’s figure of about 0.243 BTC at the CoreX-flagged address is press reporting of on-chain payments, not a Luxor total, and CoreX’s identification of OCEAN as the destination has not been matched by a public statement from OCEAN in the sources used here.
Until the promised post-mortem appears, the documented facts are the isolation to Commander, the dozen-plus accounts, the compensation pledge, and the still-unexplained vector. Readers who want a next official fact should wait for that post-mortem, not for a guessed mechanism.
Sources
- Luxor (@luxor), official statement on the Commander hashrate redirect, 17:25 GMT, 15 November 2026
- Luxor (@luxor), follow-up on isolation to Commander, 17:32 GMT, 15 November 2026
- Nick Hansen (@hash_bender), post on the Commander compromise, 17:17 GMT, 15 November 2026
- Nick Hansen (@hash_bender), thread on AI-enabled attacks, 18:04 GMT, 15 November 2026
- CoreX Hosting (@CoreX_Hosting), post flagging a miner redirect, 03:08 GMT, 15 November 2026
- Shaurya Malwa, CoinDesk, “Bitcoin Miners Were Hijacked and Their BTC Rewards Redirected to an Attacker,” 16 November 2026
- Timmy Shen, The Block, report on the Luxor Commander incident, 15 November 2026
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
- Luxor Raises $16m Led by CMT Digital to Grow Its AI Compute Trading is the TSN account of Luxor’s October funding round, which The Block also noted in its coverage of the Commander incident.
- Binance Will Shut Down Binance Pool and Related Mining Services on 10 November 2026
- FBI Names North Korea in $6bn+ Binance Hack as Withdrawals Reopen in Phases
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X




