Daily news

About 13 EH/s of Bitcoin Hashrate Hijacked and Redirected to OCEAN Pool; Luxor Commander Link Unconfirmed

About 13 EH/s of bitcoin mining power, roughly 1.4% of the network, was redirected without permission to the OCEAN pool on Nov. 15, 2026. CoreX Hosting raised the alarm and later said the attack was over. One operator blames Luxor's Commander software, which is unconfirmed. OCEAN's dashboard shows no payout yet to the reported address.

MyTraderBot DeskPublished: 8 min readخواندن به فارسی
Share
Rows of bitcoin mining machines with green status lights in a large mining farm hall, with MyTraderBot branding in the corner
Bitcoin mining farm (file photo). Photo: Marko Ahtisaari, CC BY 2.0, Wikimedia Commons
Table of Contents

About 13 exahashes per second (EH/s) of bitcoin mining power, roughly 1.4% of the network, was redirected without permission to the OCEAN mining pool early on Sunday, November 15, 2026, with mining rewards pointed at a single Bitcoin address that the hosting company which raised the alarm says belongs to the attacker. Reports put the number of affected machines at about 64,000. The incident appears to have ended within hours, but how the attacker got access is still unconfirmed, and the main suspect named by one operator, Luxor's Commander fleet-management software, had not been confirmed as the cause by Luxor at the time of writing.

This report separates what primary sources show from what is still a claim. Bitcoin itself, meaning its protocol and its blockchain, was not compromised. What was hit is the layer of software and settings that tells mining machines where to send their work.

What happened: the timeline

All times below are converted to Tehran time (UTC+3:30). The start time is based on reports and has not been independently confirmed.

  • About 05:30 Tehran, Nov. 15 (8 p.m. US Central, Nov. 14): the redirection reportedly began, according to Bitcoin News and ChainCatcher.

  • 06:38 Tehran: US hosting company CoreX Hosting posted on X that "there is a big miner hack going on as we speak," saying miners were being pointed at OCEAN with the address bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr.

  • 07:27 Tehran: CoreX wrote that the attack was ongoing, that the attacker's address was "still sitting at 13EH," and that it was switching its miners back and believed it had isolated "the program used." In a separate reply it said the problem was "not a LuxOS thing" and affected miners of all kinds, "even non-BTC miners."

  • 10:10 Tehran: CoreX said "It is over," with the attacker's address down to about 100 petahashes per second (PH/s).

  • 12:25 Tehran: an affected operator wrote that their "entire farm was hijacked" and that they could "confirm the reason was Luxor commander." This is a single user's claim; it has not been verified by Luxor or by an independent security firm.

  • Afternoon Tehran: Bitcoin News, ChainCatcher and Wu Blockchain reported the incident, all noting that a Luxor Commander compromise had not been independently confirmed.

What OCEAN's public dashboard shows

OCEAN publishes statistics for every payout address. When MyTraderBot checked the page for the reported address at about 18:10 Tehran time on Nov. 15 (14:40 UTC), it showed:

  • A 24-hour average hashrate of 1.41 EH/s, a 3-hour average of 15.28 PH/s and about 2.8 PH/s over the last 60 seconds, so a small amount of hashrate was still connected long after the peak.

  • 78,565 entries in the worker list, many named after private network addresses. That is more than the 64,000 machines in media reports; a worker entry is not necessarily one physical machine, so neither figure should be treated as an exact machine count.

  • About 28.40 trillion shares in OCEAN's reward window, equal to 2.63% of the pool's share log, with "estimated rewards in window" of 0.65825169 BTC.

  • No payouts and no earnings listed yet. The pool's last block had been found about 13 hours earlier, which would be shortly before the reported start of the attack.

For scale, mempool.space estimated total Bitcoin network hashrate at about 930 EH/s at the same time, so 13 EH/s is roughly 1.4% of the network.

Did the attacker really earn nothing?

Several reports and many posts on X say the attacker "got zero BTC" because no block was found during the hijack. That is accurate for now, but it may not be the end of the story.

OCEAN does not pay miners per share. It uses a system called TIDES. According to OCEAN's TIDES documentation, when the pool finds a block, the reward is split among the most recent shares in a "share log window" equal to eight times the network difficulty. Shares stay in that window, and can be paid for more than one block, until newer shares push them out.

So the shares created by the hijacked machines are still in the window. If OCEAN finds a block before they age out, the dashboard's own estimate suggests the reported address could receive part of the reward, up to about 0.658 BTC in total at the time we checked. OCEAN had not said publicly whether it will pay, hold or exclude those shares. Until it does, "the attacker earned nothing" should be read as "the attacker has not been paid yet."

Who lost what

The direct losers are the owners of the hijacked machines. During the redirection, their machines kept using electricity and hosting capacity, but the work went to someone else's address. Those hours of mining revenue cannot be recovered from the blockchain.

The timing is painful. Bitcoin's mining difficulty fell 9.13% on Nov. 14, the biggest cut since June, as falling prices squeezed miner margins. The bitcoin price has also been under heavy pressure; see our report on bitcoin falling below $66,000. Any lost revenue hurts more when hashprice is low.

For the Bitcoin network, the impact was limited. Blocks kept being produced, and 1.4% of hashrate is far from the majority needed for a so-called 51% attack, where one party could reorder recent transactions.

Key terms

Hashrate and EH/s

Hashrate measures how many guesses per second miners make while searching for a valid block. One exahash per second (EH/s) is a quintillion (1018) hashes per second; one petahash (PH/s) is a thousandth of that.

Mining pool

A pool combines many miners' work and shares the rewards, so each miner gets steadier income. Miners connect to a pool through a URL and a username or payout address set in each machine's configuration.

Fleet-management software

Large farms and hosting companies use software to monitor and configure thousands of machines at once, including changing pool settings. Luxor markets Commander for this purpose. If any such tool, or the passwords and API keys behind it, is compromised, one change can redirect a whole fleet. This is why the incident is being described as an operational-security failure rather than a flaw in Bitcoin.

Claims versus confirmed facts

Confirmed by primary sources: CoreX Hosting publicly reported unauthorized redirection to OCEAN and later said it was over; OCEAN's dashboard shows large shares and tens of thousands of workers on the reported address, with no payouts yet.

Reported but not confirmed: the 64,000-machine figure, the exact start time, and the claim that Luxor Commander was the entry point. CoreX itself declined to name the software publicly, writing that it was "not qualified enough to point fingers." CoreX also said it uses three different management programs. ChainCatcher reported that other operators described similar unauthorized pool changes several days earlier, which, if confirmed, would suggest a wider campaign.

No public statement yet: MyTraderBot found no public statement from Luxor or OCEAN about the incident at the time of writing.

What miners and hosting clients can do

  • Check each machine's pool URL, worker name and payout address against your records, and look for changes made since early November.

  • Rotate passwords and API keys for management dashboards, firmware web interfaces and hosting portals, and turn on two-factor authentication where available.

  • Keep miner management interfaces off the public internet and restrict access by network.

  • Compare expected hashrate with what your pool dashboard shows; a sudden drop is often the first sign of redirection.

  • If you are a hosting client, ask your host which management software it uses and whether your machines were affected.

Do not send funds to, or interact with, the address named in this report. It is listed only so operators can recognize it in their own configurations.

What to watch next

  • Whether Luxor confirms or rules out a Commander compromise, and whether it publishes a post-mortem.

  • Whether OCEAN pays, freezes or excludes the shares tied to the reported address when it finds its next block.

  • Whether more hosting companies or farms report being affected, and whether the earlier unauthorized changes are linked.

  • Any guidance from firmware makers on locking pool settings.

FAQ

Was Bitcoin hacked?

No. The Bitcoin protocol and blockchain were not breached. The attack changed the settings of mining machines so that their work went to a different payout address.

Could this lead to a 51% attack?

Not at this scale. About 13 EH/s is roughly 1.4% of network hashrate. A 51% attack would need majority control, far beyond what was reported here.

Do bitcoin holders need to do anything?

No action is needed for ordinary holders. The incident affects mining operators and hosting clients.

This article is news reporting, not investment advice. Details may change as the companies involved respond.

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.

13 EH/s of Bitcoin Hashrate Hijacked to OCEAN Pool: What We…