Security

Crypto's 2026 Breaches: It's the Keys, Not the Code

Key and credential leaks cost crypto $130M in H1 2026. The numbers behind November's API key breaches, and why a payout with no balance is different.

A transfer needs more than a key: a route with an API key plus a wallet signature reaches a lit green exit; a key-only route ends at a gray exit. Tess reads a receipt at lower right.

Here is the number that should worry anyone holding crypto on someone else's platform: $130 million. That is what the security firm SlowMist counted in losses from private key and credential compromises across the industry in the first six months of 2026, spread across 17 separate incidents. SlowMist files these apart from smart contract bugs. In each one, the contract logic was not the way in. A key or a login ended up somewhere it shouldn't have been.

November 2026 has already added two crypto API key breach cases to that pattern. This post walks through the actual figures, because the scale of the problem is easier to see in the numbers than in the headlines, and because the numbers point at one design question every miner and trader should ask about whatever platform holds their funds: what, exactly, does a leaked credential let someone do?

The Number: $130 Million Across 17 Credential Incidents

SlowMist's mid-year report counted 182 security incidents in the first half of 2026, with about $956 million in losses. Contract and logic bugs were the most common cause, with 85 incidents and about $152 million lost. Private key and credential compromise came second by count, with 17 incidents and about $130 million. Supply chain attacks caused the largest losses, about $298 million, almost all of it from a single $292 million cross-chain incident.

The average is where credentials stand out. $130,000,000 divided by 17 is $7,647,058.82, about $7.6 million per credential incident. $152.3 million divided by 85 is about $1.79 million per contract bug. A typical stolen key or login cost about four times as much as a typical code flaw. Individual losses varied widely around both averages, so treat them as a measure of scale, not a prediction.

Incident Date Reported loss Root cause
H1 2026 credential compromises (SlowMist) Jan-Jun 2026 ~$130,000,000 across 17 incidents Private keys and credentials leaked
H1 2026 contract and logic bugs (SlowMist) Jan-Jun 2026 ~$152,000,000 across 85 incidents Flaws in contract code
SignalPlus Nov 4-5, 2026 Under $82,000, reimbursed Engineer's machine compromised via a fake meeting invite; exchange API keys without IP allowlists
Lighter (perpetuals exchange) Nov 16, 2026 ~$10.4M withdrawn, ~$5M returned Custom signing software reused nonces, exposing a trader's API key

November Alone: Two API Key Breaches, One Playbook

On November 4, 2026, attackers reached the options trading terminal SignalPlus through a fake Microsoft Teams meeting invitation sent to one of its engineers from a vendor contact's hijacked Telegram account. The intrusion gave them a path to exchange API keys linked to the terminal. SignalPlus said the loss came to just under $82,000, pledged to reimburse affected users in full, and paused its service for a security review. It also admitted it had not required IP allowlists for exchange API access. Binance and Deribit revoked every SignalPlus-linked API key the next day, which is itself a telling detail: the fastest fix anyone had was to kill the credential, not patch a cipher.

Twelve days later, a larger version of the same failure hit Lighter, a perpetual-futures exchange. According to CoinDesk's report on the incident, Lighter paused withdrawals on November 16 after a trader's API key leaked. Analytics firms Bubblemaps and Bitquery traced about $10.4 million in USDC leaving the exchange. Other analysts estimated $15.5 million across two market-maker accounts, a figure Lighter has not confirmed.

Lighter's postmortem explains how the key leaked. The trader signed with custom software from outside Lighter's official kits, and that software reused nonces, the one-time values every signature needs. Two public signatures made with the same key and the same nonce let anyone calculate the private key. With that key alone, the attacker opened a public pool from the trader's account, moved the trader's money into it, and redeemed it through an account they controlled. Lighter's contracts, protocol and official software were not affected. Its Guardian pause let the exchange's Security Council return about $5 million in USDC to the trader, and withdrawals reopened the same day. A transfer into a public pool now needs a wallet signature, API key signatures are no longer public, and IP allowlists and per-key permissions are on the way.

That same week, a company that remotely manages mining rigs for hosting customers had its fleet-management software breached, and an intruder briefly redirected a slice of connected hardware to another destination before access was cut off. Different industry, same shape: the mining protocol held, and the access layer around it did not.

The Math Behind a Leaked Key

Lighter's case draws the line precisely. Nobody broke the signature scheme. A piece of signing software misused it by reusing a nonce, and recovering a key from that mistake is textbook arithmetic. Forging a signature under a correctly used scheme is not a realistic path to crypto theft in 2026. Finding one key that was handled carelessly, or one engineer who clicks a fake meeting link, is a realistic path, and the $130 million figure above is the result. An attacker doesn't need better math than the people they target. They need the target to leave a credential more exposed than the scheme itself.

This is also why the fixes at SignalPlus and Lighter weren't new cryptographic primitives. They removed capabilities: no transfer into a public pool without a wallet signature, no public view of API key signatures, and IP allowlists that SignalPlus admitted it had not required. Capabilities, not code, are what a stolen credential buys.

What a Stolen API Key Can't Reach at NexusPool

A useful follow-up question is what happens when there's no capability to steal in the first place, because there's no account balance sitting behind the credential. NexusPool is built around that gap. Mining is non-custodial: with a 0% pool fee, the coinbase transaction that pays out a found block goes straight to the miner's own address, and NexusPool's Payout Preflight tool lets a miner see that exact coinbase, built by the same code that would build a real block, before any block is ever found. There is no pool-held balance for a leaked credential to redirect, because there is no pool-held balance at all.

The connection between a rig and the pool is handled the same way. NexusPool runs native Stratum V1 and Stratum V2, and the V2 connections are encrypted and pinned to an authority key the pool publishes, not a revocable secret sitting in a dashboard. Readers can see how that connection is built on NexusPool's technology page. On the accounting side, each hour NexusPool signs a Glass Ledger receipt for every rig: the shares it counted, the difficulty they were served at, and the window they landed in, checkable against a key the pool publishes. None of this makes NexusPool, or any platform, immune to every future attack. It does mean the failure mode behind this month's two cases, a working credential unlocking someone else's balance, has no balance to unlock here.

To be clear about what this post is not claiming: it is not investment advice. Nothing described above changes the odds of finding a block, which depend only on a miner's hashrate and the network difficulty, the same at every pool. NexusPool's own source code is not public. Nothing here claims NexusPool has prevented a hack on another platform, only that its design removes one category of thing to steal.

What To Actually Check

The $7.6 million average loss per credential incident in H1 2026 is not a reason to panic about every platform you use. It is a reason to run one specific check: for any API key tied to any crypto account, does it have withdrawal or transfer permission it doesn't need, is it locked to the IP addresses you actually use, and does a transfer to a new address require anything beyond that key alone? If the key has more permission than the task requires, or nothing stands behind it but the key, it is worth the same to an attacker as the ones behind this month's two incidents. Check the software that signs with it, too: Lighter's trader lost the key through a signing tool, not through the exchange. For a non-custodial setup where nothing sits in a balance to begin with, the withdrawal question doesn't apply, which is the whole point of not holding one.

Trust nothing. Verify what a leaked key could actually reach.