TL;DR: On the night of Saturday, November 14, 2026, an attacker broke into Luxor Technology's Commander fleet-management software and repointed the Bitcoin mining machines of just over a dozen client accounts at the OCEAN mining pool, with payouts set to a single address the attacker controlled. Early reports put the scale at about 64,000 machines and roughly 13 exahashes per second (EH/s), about 1.4% of the network — figures Luxor has not confirmed. The machines never found a block, yet the address still collected four OCEAN payouts totaling 0.32445584 BTC, about $21,000, because OCEAN's TIDES system keeps paying for work already submitted. Luxor patched Commander within two hours and promised full compensation. OCEAN says it was not compromised.
Last updated: November 2026
Key Takeaways:
- The attack hit a management dashboard, not Bitcoin. Changing two fields — pool address and payout username — redirected the machines' income while they kept running normally.
- The scale is reported, not confirmed. About 64,000 machines and roughly 13 EH/s come from early reports; Luxor confirms only "just over a dozen client accounts."
- The attacker got paid without finding a block. OCEAN's TIDES system splits each block reward across a rolling log of recent work, so shares submitted during the hijack kept earning on later blocks.
- The on-chain total is 0.32445584 BTC across four payouts, about $21,000 at November 18 prices. One payout was spent on November 17; the other three were unspent.
- Three parties, three stories: Luxor says it patched in two hours and will pay clients in full; OCEAN says it was not compromised; its former co-founder Luke Dashjr accuses the pool of profiting.
Most crypto hacks are described as stolen keys or broken smart contracts. The OCEAN incident was neither. On the night of Saturday, November 14, 2026, someone broke into the software that manages other people's Bitcoin mining machines and quietly changed where those machines send their work. The only thing that changed was who got paid.
It did not break Bitcoin, and it did not empty a single wallet. It exploited the layer in between: the centralized management tools that run thousands of machines at once. One compromised console turned other people's hardware into a short-term income stream — and the pool's payout rules kept paying the attacker for hours after the hijack was stopped.
What Is Luxor Commander?
Commander is Luxor Technology's fleet-management tool, launched in April 2026, for operators who managed pools, firmware, and power settings through separate vendors. From one console, an operator can reboot or sleep machines, update firmware, and — the feature that matters here — change pool settings for thousands of miners in a single bulk operation.
A Bitcoin mining machine is configured with a small number of settings that decide where its work goes: a pool address and a username, which on OCEAN is simply a Bitcoin address. The machine hashes, submits its shares to that pool, and the pool pays that address. Nothing in the machine checks whether the address belongs to its owner.
One console that can repoint thousands of machines saves an operator hours of manual work — and does the same for an intruder. Commander was the single point of failure: whoever could issue commands through it could redirect every machine connected to it.
How the Hijack Worked, Step by Step
The precise entry point is still undisclosed, but the shape of the attack is confirmed by Luxor and visible on chain. Sometime on Saturday evening, November 14, an attacker gained the ability to issue commands through Commander. The commands changed the pool settings on machines belonging to just over a dozen Luxor client accounts, pointing them at OCEAN and setting the payout username to a single Bitcoin address the attacker controlled: bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr.
The machines did what they were told. They connected to OCEAN and began submitting shares, exactly as they would have for their real owners. OCEAN's hashrate jumped to about 50 EH/s before settling near 40 EH/s, against a pool that normally runs at roughly 2% of the global network. The attacker's address briefly registered close to 14 EH/s — roughly 1.4% of the network's 942 EH/s. Large for a single incident, and nowhere near enough to threaten the chain itself.
Nothing was stolen from a wallet, and no block was altered. What was diverted was the future income of the machines. This is also why the usual alarms did not fire: a repointed machine does not overheat, slow down, or go offline. The only signal was on the pool side — machines that should have been mining elsewhere submitting shares to OCEAN under one unfamiliar address.
The pattern is familiar: miners earn money from their position in the system, and attackers look for ways to capture that income without breaking the underlying cryptography — the same idea, in a different form, behind MEV bots that watch pending transactions and reorder them to extract value. Here the position being exploited was not transaction ordering but fleet configuration: whoever controls the settings controls the revenue.
Timeline: Saturday Night to Wednesday Morning
| Date and time (UTC) | Event |
|---|---|
| Sat Nov 14, about 18:00 Pacific (02:00 UTC Nov 15) | Compromise begins; machines are repointed to OCEAN under a single attacker address. |
| Sun Nov 15, 03:08 | CoreX Hosting raises the first public alarm on X: "a big miner hack going on as we speak." |
| Sun Nov 15, about 06:40 | CoreX says the attack is over, with about 100 PH/s still pointed at OCEAN. |
| Sun Nov 15, 17:22 | OCEAN finds block 975,995. Its coinbase pays 0.08088977 BTC to the attacker address. |
| Sun Nov 15, 17:25 | Luxor confirms the breach: an unauthorized redirect of hashrate through Commander, just over a dozen accounts affected, patched within two hours, full compensation promised. |
| Sun Nov 15, 22:54 | OCEAN finds block 976,029. Second payout to the attacker address: 0.08113106 BTC. |
| Mon Nov 16, 06:26 | OCEAN finds block 976,084. Third payout: 0.08106822 BTC. |
| Mon Nov 16, 08:17 | OCEAN finds block 976,097. Fourth payout: 0.08136679 BTC. Total to the address now 0.32445584 BTC. |
| Mon Nov 16 | OCEAN states on X that it was not compromised and credit for valid work cannot be reassigned. Former co-founder Luke Dashjr accuses the pool of profiting. |
| Tue Nov 17, 10:42 | The fourth payout is spent into three outputs. The other three payouts remain unspent. |
| Wed Nov 18 | No full post-mortem from Luxor yet. A few machines, about 0.5 PH/s, are still mining for the attacker address. |
How the Attacker Got Paid Without Finding a Block
The attacker's machines never solved a block. Early coverage on Sunday even reported that the attackers had earned nothing. That changed within hours, and the reason is how OCEAN pays its miners.
Most large pools hold the reward and distribute it. OCEAN is different. It is a non-custodial pool: when it finds a block, the payout goes directly from the block's coinbase transaction — the first transaction in the block, the one that creates new bitcoin — to each miner's wallet address. OCEAN never holds the funds and requires no account.
The split is calculated by a system OCEAN calls TIDES, short for Transparent Index of Distinct Extended Shares. Every share a machine submits is recorded in a continuous log, and when OCEAN finds a block, the reward — the 3.125 BTC subsidy plus transaction fees — is split across the most recent eight times the network difficulty worth of shares in that log. Your percentage of the window is your percentage of the block reward. The window is large by design: every share has a 99.9665% chance of being rewarded at least once, and on average eight times.
That design is why the payments kept coming after Luxor patched Commander. Shares keep earning on every block the pool finds until they slide out of the log, even if the machines behind them have disconnected. The hijacked machines submitted a large volume of shares in a few hours — OCEAN's page credited the attacker address with 28.51 trillion shares, or 2.64% of the reward window, on Monday morning — and those shares were still in the window when OCEAN found its next blocks. The four payouts below are all visible on mempool.space:
| Block | Found (UTC) | Paid to the attacker address |
|---|---|---|
| 975,995 | Nov 15, 17:22 | 0.08088977 BTC |
| 976,029 | Nov 15, 22:54 | 0.08113106 BTC |
| 976,084 | Nov 16, 06:26 | 0.08106822 BTC |
| 976,097 | Nov 16, 08:17 | 0.08136679 BTC |
| Total | 0.32445584 BTC, about $21,000 at November 18 prices |
After the second payout the address held 0.16202083 BTC, about $10,500 — the figure most early reports used. The next two blocks doubled it. One payout was spent on Tuesday, November 17, at 10:42 UTC, split into three outputs. The other three payouts, 0.24308905 BTC together, were unspent as of Wednesday morning.
OCEAN's statistics page also shows the tail of the incident: a handful of machines were still mining for the attacker address days later — eight workers at about 2 PH/s on Monday, three at about 0.5 PH/s on Wednesday.
Which Numbers Should You Trust?
The figures in this story are not equally solid:
| Item | Figure | Status |
|---|---|---|
| Client accounts affected | Just over a dozen | Confirmed by Luxor |
| Time to patch | Within two hours | Confirmed by Luxor |
| Machines redirected | About 64,000 | Early reports relayed by Cointelegraph; not confirmed by Luxor |
| Hashrate redirected | About 13 EH/s, about 1.4% of the network | Early reports relayed by Cointelegraph; not confirmed by Luxor |
| Paid to the attacker address | 0.32445584 BTC in four payouts | Verifiable on chain via mempool.space |
| Attack vector | "A sophisticated AI-enabled vector" | Claimed by Luxor's CEO; no detail disclosed |
| Miners compensated | In full, "as if it had mined normally" | Promised by Luxor; no confirmation of payments yet |
What Luxor, OCEAN, and Dashjr Said
Luxor confirmed the breach in a statement on X at 17:25 UTC on Sunday. Its monitoring had caught "an unauthorized redirect of hashrate through Commander," engineers patched the software within two hours, and the team began restoring machines to their original pool settings. The statement said no data left its systems, that Commander was "operating normally and no action is needed from users," and that every affected client would be paid "as if it had mined normally." A full post-mortem was promised, with no date. Luxor added on Monday that the problem "was isolated to the Commander tool."
Chief executive Nick Hansen gave the start time in his own post at 17:17 UTC on Sunday: "Around 6:00p PDT yesterday." He wrote PDT, but the US Pacific coast had been on standard time since November 1, so 6 p.m. there is 02:00 UTC on Sunday — meaning CoreX's warning came about an hour after the first machines were redirected. Hansen called the entry point "a sophisticated AI-enabled vector." Neither he nor Luxor has explained what that means: which flaw was used, how the attackers reached client accounts, or what part AI tools played. Luxor has paused most new feature work to harden its infrastructure, he wrote, listing key rotation, kernel updates, and pinned dependencies.
OCEAN answered on Monday, November 16, in a statement on X. The pool acknowledges that hashrate belonging to Luxor and its customers was redirected without authorization to other pools, itself included, and denies any involvement. "Ocean was not compromised. Our systems operated normally," the statement reads. On the payouts, its position is that it has no say: TIDES checks that the work submitted is valid, not who owns the machines. Once valid work is in the log, the credit cannot be reassigned. "Permissionless mining isn't a loophole. It's a principle," it wrote. OCEAN says it will cooperate with Luxor, law enforcement, and affected customers.
Luke Dashjr, the Bitcoin developer who co-founded OCEAN and served as its chairman before leaving in August 2026 over a disagreement about the BIP-110 protocol direction, went through the pool's numbers in a post on X on Monday, after the second payout. By his count, as relayed by Bitcoin.com News, OCEAN had directed 0.16202083 BTC to the attackers in two payments and was allocating a further 0.08123485 BTC. He put the pool's own fees at about 0.01 BTC in total, roughly $650. "Ocean is profiting from a cyberattack on their own customers, and rewarding the attackers," he wrote.
Why This Is Not a 51% Attack — and Not a Smart Contract Hack
A 51% attack means one party controls a majority of the network's hashrate and can rewrite recent history: censor transactions, reverse its own payments, and double-spend. Thirteen EH/s is about 1.4% of the network. It cannot reorder blocks, censor anyone, or change a single transaction.
The incident also belongs to a different family than the other two big exploits of the same week. Each one fails at a different layer:
| Incident | What broke | What was taken |
|---|---|---|
| OCEAN hijack, Nov 15 | Fleet-management software (Luxor Commander) | Future mining income: 0.32445584 BTC paid out |
| Kava Lend, Nov 14 | Arithmetic in a lending module that divided by net supply | About 55.2 million KAVA borrowed against phantom collateral |
| Across Protocol, Nov 10 | Domain registrar account, taken by social engineering | An estimated $402,000 from nine wallets |
The Kava Lend exploit drained about $3.76 million from a lending protocol through an arithmetic bug: a function that divided interest by net supply and only refused when the supply was exactly zero, so an attacker set it to two base units and inflated a dormant BUSD market about 243,000-fold. The Across Protocol attack took over a bridge's domain through social engineering at its registrar and served a fake app for about three hours; no smart contract was touched. The OCEAN incident is a third shape: an infrastructure compromise. The attacker took over the control plane — the dashboard that tells machines what to do — and the machines obeyed.
That is the lesson that generalizes. Crypto security is usually discussed as keys and contracts, but the systems around them — registrars, fleet dashboards, admin panels, bridge interfaces — are where the leverage now sits. Each one is a single point of failure that can redirect other people's assets without breaking any cryptography. Redirecting miners is an old trick: researchers documented a similar hijack as early as August 2014. What is new is the scale a single cloud console can deliver.
What Miners and Pool Operators Should Check
If you run mining machines through a fleet-management tool, this incident is a checklist, not a spectator event:
- Alert on pool changes, not just downtime. A machine that stops hashing triggers every monitoring system; a machine that switches pools triggers almost none. Alert on any change to pool address, payout username, or worker name.
- Verify the payout address out of band. Check the address your machines are mining to against the pool's own statistics page, from a separate device.
- Limit who can issue bulk commands. Bulk actions are the feature that made this attack scale. If your fleet tool supports approval for bulk changes, turn it on. A single compromised account should not be able to repoint a whole fleet.
- Separate the management plane from the money. The payout address should not be changeable from the same console session that manages power and firmware without additional authentication.
- Watch for small stragglers after an incident. Days after Luxor patched Commander, a few machines were still mining for the attacker address. Audit every machine's configuration, not just the accounts you know were affected.
- Know your pool's payout rules before you need them. OCEAN's TIDES system pays from a rolling log of past work, so stolen shares keep earning after the theft is stopped. Other pools hold funds and can freeze payouts.
None of this is financial advice. If you mine through a third-party tool, the question is not whether the tool is convenient. It is what happens when someone else holds its keys.
Frequently Asked Questions
Was Bitcoin itself hacked?
No. No block was altered, no coins were taken from any wallet, and the network kept running. The attacker compromised Luxor's Commander fleet-management software and changed the pool settings on other people's mining machines. Bitcoin's cryptography and consensus were untouched.
How much did the attacker actually get?
0.32445584 BTC across four OCEAN payouts, about $21,000 at November 18 prices. The first two totaled 0.16202083 BTC, about $10,500, and the next two doubled it. One payout was spent on November 17; the other three were unspent as of November 18.
Why did OCEAN pay the attacker after the hijack was stopped?
Because of how TIDES works. OCEAN splits each block reward across a rolling log of recent work, and shares keep earning on every block the pool finds until they slide out of the log — even if the machines behind them have left. Payouts come directly from the coinbase, so there was no pool wallet to freeze.
Will the affected miners be paid?
Luxor has promised to pay every affected client in full, "as if it had mined normally," and says affected clients would receive an email with compensation details. As of November 18, no confirmation of actual payments has appeared.
Could this happen to my mining operation?
If your machines are managed through a cloud fleet tool, yes, in principle. The defense is monitoring for configuration changes rather than just downtime, verifying your payout address on the pool's statistics page, and limiting who can issue bulk commands. Pointing machines at a pool directly removes the central console — but also the bulk management features.
What is still unknown?
Several things. Luxor has not disclosed the attack vector beyond calling it "a sophisticated AI-enabled vector," and its full post-mortem has no date. The 64,000-machine and 13 EH/s figures remain unconfirmed. It is not known who controls the attacker address or the few machines still mining for it, or whether law enforcement will recover the payout spent on November 17.
Sources
- Coindaro: Luxor Commander hack: client hashrate redirected to OCEAN (November 16, 2026, updated November 18, 2026)
- Crypto Coin Show: Attacker cashed out 0.162 BTC from OCEAN pool without mining any blocks (November 16, 2026)
- CryptoSpiel: Luxor Hack Sent Clients' Bitcoin Miners to Work for a Thief (November 16, 2026)
- PlainBTC: Luxor Commander breach: hijacked bitcoin miners sent about 13 EH/s to the OCEAN pool (November 15, 2026)
- Mitrade: How Did a Bitcoin Miner Hacker Get Paid Without Finding a Single Block? (November 16, 2026)
- iFynx: 64,000 Bitcoin Miners Hijacked: 13 EH/s Sent to OCEAN (November 15, 2026)
- SAZ Mining: How OCEAN Payouts Work: Understanding TIDES and Why It's Different (accessed November 2026)
- D-Central: OCEAN Mining Pool Review & Setup Guide 2026 (accessed November 2026)

