Security

Mining Hashrate Hijack: One Dashboard Repointed the Rigs

A breach of a fleet-management dashboard sent about 13 EH/s of mining hashrate to another pool. Check who can repoint your rigs and what you can verify.

One dashboard can repoint a whole fleet: a green chain of blocks keeps its course on the teal route while a gray branch splits off and fades. Tess reads a receipt at lower right.

Around 6 p.m. Pacific time on Saturday, November 14, 2026, mining rigs on more than a dozen customer accounts of a remote fleet-management platform began sending their work to a pool their owners had not chosen. The machines kept hashing and the owners kept paying for power. Nobody on the customer side had changed a setting. An attacker had changed it for them, through the platform. It was a mining hashrate hijack, and the attacker never touched a rig.

The company behind the platform confirmed the breach on Sunday, November 15. Its internal monitoring flagged an unauthorized redirect of hashrate, its engineers patched the flaw within two hours, and they began restoring the affected machines to their original pool settings that night. The company says no data left its systems, that the problem stayed inside the fleet tool, and that it will pay every affected client in full for the redirected hashrate, as if the rigs had mined as configured. Its chief executive described the entry point as a "sophisticated AI-enabled vector" and has not explained how the attacker used AI or got in. The company has promised a post-mortem.

The chief executive told one outlet the redirected hashrate came to about 13 EH/s, worth about $20,000 an hour. Outlets put that near 1.4% to 1.5% of Bitcoin's network hashrate. A figure of 64,000 machines also circulated over the weekend. It comes from a third-party estimate and the company has not confirmed it. CoinDesk's report on the redirected rewards adds that a bitcoin address tied to the redirect had received three payouts totalling about 0.243 BTC, about $15,700, and had spent none of it by Monday morning. Under the destination pool's payout rules, work submitted during the window stays eligible for a share of later blocks, so payments could keep arriving after the rigs went back to their owners' settings.

Nobody has accused the destination pool of anything. A pool that receives redirected hashrate cannot tell that the rigs' owner did not send it, and nothing in this piece says otherwise.

A hashrate hijack needs one switch

A fleet-management platform lets one operator repoint hundreds or thousands of machines from one screen, without walking a server room. An attacker who gets into that screen inherits the same reach. They need no rig password and no private key. They need the one panel the rigs obey. On Saturday the rigs did what the panel told them, and for a limited window the panel took orders from someone else.

Most home and hobby miners run no third-party fleet software. The incident still hands you a question for your own setup: count the parties, software layers and remote panels that can change the pool URL or the payout address on your rig. The miner's own web interface is one. Custom firmware with remote management is another. A cloud monitoring app with write access is a third. Each one can turn "my rig points at my pool" from a fact into an assumption. Four checks cover most home setups:

  • Read the setting on the rig. Open the miner's own interface and read the pool URL and the payout address there, whatever a remote panel shows.
  • List who can change it. Put every account, API key and app with write access to pool settings on that list, and remove the ones you don't use.
  • Change the factory login. A rig on your network with the default password is its own open panel.
  • Watch the pool side. If your pool shows no shares from a rig that is hashing, the work is going somewhere else.

How NexusPool connects a rig to the pool

A rig connects straight to NexusPool over native Stratum V1 or Stratum V2 on the same port, and the pool detects which protocol the rig speaks. NexusPool's technology page describes that connection. NexusPool requires no fleet-management layer and no account between the rig and the pool. Your Bitcoin address is the identity, and NexusPool is a solo, non-custodial pool: the reward for a block your rig finds pays to that address in the block's own coinbase transaction, and the pool never holds it. Payout Preflight tests that payout address before a block depends on it.

That removes one layer, and only one. If you run fleet software or remote-managed firmware, that layer exists whichever pool you point at, and NexusPool cannot see it or guard it. NexusPool's own software has attack surface too, like any software.

What you can check without a dashboard

NexusPool signs a receipt every hour for each rig. A Glass Ledger receipt is a BIP340-signed record of the shares the pool counted from that rig in that hour, and at what difficulty. You can verify the signature against the key NexusPool publishes with any BIP340 library. A dashboard shows what its operator, or its attacker, tells it to show. A receipt for an hour in which your rig's work went elsewhere shows the missing shares, and nobody can edit it afterward without breaking the signature. The receipt covers what NexusPool counted. It says nothing about where else a rig's hash went.

This piece describes an incident that the affected platform disclosed and that several outlets covered as of November 16, 2026. It accuses nobody at the destination pool. It is not financial advice. It makes no claim that NexusPool's software is open source, and a direct connection does not make a rig immune to future attacks on mining infrastructure.

On Saturday evening the rigs on those accounts kept hashing while their work paid someone else. The company patched the flaw within two hours because its own monitoring watched where the hashrate went. You can do the same at your scale: read the pool URL on the rig, know who can change it, and keep a record that does not depend on the panel.

Trust nothing. Verify where your hashrate points on the rig itself, and who else can change it.