Crypto Hacks 2026: The $6.3B Binance Breach, Record Attacks and Where AI Fits In

How Many Crypto Hacks in 2026, and How Much Has Been Stolen So Far

Crypto hacks in 2026 total a record $8.7B by TRM's October 30 count, and Binance's $6.36B theft is most of it. Without Binance, ten months of 2026 cost about $2.3B, roughly what H1 2025 alone lost. The H1 dip reflected one missing outlier; underlying risk never fell.

The first half of 2026 set the frequency record. TRM Labs counted 207 incidents in H1 2026, up from about 83 a year earlier, with $972M stolen against $2.3B in H1 2025, and warned that the drop only reflected the absence of a 2025-scale theft.

Binance's breach pushed TRM's year-to-date total to a record $8.7B, about 31% of the roughly $28B ever stolen in crypto. Subtracting TRM's $6.36B Binance figure, a number no vendor publishes, leaves 2026 near $2.3B.

The two H1 headlines differ by method. TRM keeps the $1.5B Bybit theft in its 2025 base, so H1 2026 reads −57%, while CertiK strips Bybit and reads +28%. CertiK's Q3 dashboard, last updated before Binance, adds $1.28B across 255 incidents. We never compare across vendors.

Our own count, built from public incident reports and posted on November 3, lands close to TRM's: $8.78B stolen in 328 hacks, with Binance at 72% of it.

2026 is already the worst year on record: $8.78B stolen in 328 hacks. More than 2021–2023 combined. Binance alone is 72% of it.

North Korea accounts for 85% of 2026 stolen value with Binance, about 45% without it, by TRM's count: $7.4B this year and $12.8B all-time. TRM notes that only 13 of its 100 DPRK thefts since 2017 exploited contract code.

TRM counted smart-contract exploits in 125 of 207 incidents, yet they carried a far smaller share of the money, and Blockaid's own H1 2026 report puts operational security attacks behind 74% of $1.1B stolen across 212 incidents. Polymarket's 2026 incidents fit that split, with user losses coming from its website rather than its contracts, as we lay out in our Polymarket hack review.

DropsTab Research's public Lazarus Group portfolio records the group's earlier attributed hauls, led by the 2025 Bybit theft; how to follow it is in the last section.

The Binance Hack, and What Did the Freeze Button Recover

The Binance hack of October 29, 2026 drained about $6.3B, the largest crypto theft on record. Issuer freezes locked roughly 42–45% within hours, stablecoins almost only. Binance is repaying users from its own funds, and the frozen money has not moved.

How Binance got hacked

The size depends on who counted: about $6.34B by Binance, $6.36B by TRM, about $6.4B by Chainalysis and $6.43B across 11 chains by Elliptic. The core drain took about 20 minutes from 20:05 UTC, by TRM's count, but the attacker's code ran Binance's main Ethereum wallet until 23:56 UTC.

TRM, Fireblocks and Blockaid classify the breach as a signing-infrastructure compromise with no smart-contract exploit. At 20:20 UTC a single transaction carried 50 pre-signed EIP-7702 authorizations from a Binance hot wallet, "so at least one would be valid when processed," in Fireblocks' reading. EIP-7702, live since May 2025, lets one signature hand a wallet's code to a contract.

The batch handed the wallet to an attacker's sweeper contract, which took 167,464 ETH and $1.615B USDT in one transaction, then 780M USDC from a second wallet. TRM traces the preparation back at least 36 hours, funded through Tornado Cash.

Binance's account of the entry point changed twice. Its first post named one compromised machine.

Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer's laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak.

Binance's follow-up the same day reported more points of breach.

Investigation update: Our initial investigation suggested that the security incident may have involved a compromised laptop, however our subsequent investigation has uncovered additional points of breach. … The outflows ceased when we paused withdrawal service earlier. We are still working with partners to freeze many of the impacted assets, and have frozen around $3 billion thus far.

Binance's initial findings, published November 3 on its X account, describe a months-long campaign:

• June 2026, a poisoned installer. A Wallet DevOps engineer searched for a popular AI coding tool and downloaded a tampered Homebrew installation. Binance caught it, replaced the device and rotated credentials, but the attackers had already learned who worked on the wallet team.
• September, a fake job interview. A second engineer was approached on a job-hunting platform, sat two rounds of interviews with a fictitious company and downloaded a test "assignment" onto his work computer. Binance says its endpoint protection missed the zero-day malware inside.
• October 20, an internal AI tool as a springboard. From that computer the attackers used a Binance internal AI tool to take control of the first engineer and a third one, and found a container deployment token on the DevOps engineer's machine.
• October 29, the signing service. Between 17:15 and 19:56 UTC they logged onto the third engineer's computer, deployed a container with the stolen credentials and launched the script that reached the wallet signing service.

The report also corrects the October 30 line that outflows stopped when withdrawals paused. The EIP-7702 delegations lived on-chain and kept working outside Binance's withdrawal system, and with an MPC (multi-party computation) hot wallet there was no single key to revoke them at once. The findings are Binance's own and preliminary, pending an independent review.

Why the attacker swapped stablecoins for ETH

The attacker raced to swap stablecoins before the issuers could freeze them. By Bitquery's count, $729M of stolen USDT escaped before the freezes landed. 495M went into ETH through UniswapX and 1inch at about a 16% overpay, and 234M into TRX on SunSwap, and the rush cost the attacker about $119M against market prices. Elliptic and Hacken put the pre-freeze conversion near $786M.

Aave let the attacker turn freezable USDT into ETH. The attacker supplied 60M USDT to Aave V3 and borrowed 19,762 WETH, about $44.6M, per the Aave governance record. A wallet blacklist cannot reach collateral pooled in Aave's shared reserve, and the position was still open on November 3.

Chainalysis tracked the same playbook as it happened.

The Binance exploiters are rushing to stay a step of stablecoin freezes. One method we're tracking involves stashing their stablecoins in DeFi protocols. Then claiming them back on new, clean addresses. … Circle and Tether have already contributed to $2.8 billion in freezes so far. … swapping freezable stablecoins on one side with unfreezable ETH on the other.

How the stolen funds moved through Tron

About $628M of the haul sat on Tron, about 613M USDT plus 46M TRX by TRM's count, and Tether froze about 379M USDT there by Bitquery's count. Elliptic measured payouts of $7M to $11M per hour for 31 unbroken hours across roughly 200 wallets, "almost certainly software-driven."

Every issuer with a button pressed it inside the first hour. Tether's CEO Paolo Ardoino posted the company's first freeze count at 21:25 UTC on October 29.

Tether froze more than 1.567B USDT related to a potential Binance exchange hack. Protecting the industry and our partners is our main priority.

That first count covered all chains and climbed to about 1.76B USDT. Circle froze 823M USDC, WLFI locked 27.8M of its USD1, the Arbitrum Security Council froze about $30M, and Ripple froze 40.5M RLUSD. Together, the freezes come to about $2.7B, or 42% of the haul, by TRM's count, and $2.85B, or 44–45%, by Elliptic's and Binance's.

Two months before Binance, Cronos went further than any issuer: its validators halted the network and rolled it back 10,961 blocks, almost two hours of history, to undo the Tectonic exploit. The rollback reversed about $111.2M, erased unrelated transactions from the same window, and missed about $9.19M that had already left through bridges.

The DropsTab team has mapped 15 such overrides, from The DAO fork in 2016 to the Arbitrum Security Council's move on the Binance hacker's funds.

Not your keys, not your coins. Unless the chain says otherwise. This week Arbitrum moved the Binance hacker’s $30M. No key, no signature. Second time this year.

Nothing frozen had been released as of November 3. Bitquery's snapshot that day puts about $3.0B still attacker-held, $1.40B in BTC, $1.22B in ETH, $292M in XRP and $75M in SOL. The ETH stack, about 540,000 tokens, includes ETH bought with the swapped stablecoins.

If you hold USDT or USDC, its issuer can freeze your balance the same way.

Attribution and Binance's response

Attribution remains an assessment, and we treat it as one. TRM assesses with high confidence that DPRK's TraderTraitor carried out the theft, and Chainalysis posted its own read.

Our investigators observed funds stolen by DPRK in last month's Bitget exploit commingling with funds stolen from Binance. We have a high degree of confidence that DPRK is responsible for the $6.4 billion hack of Binance.

An FBI alert of October 31 says North Korea was responsible for the theft of more than $6 billion and published the attacker address list. Binance's November 3 report cites the FBI's finding that North Korea is responsible, while North Korea has denied the claims.

Binance pledged to cover all losses from its SAFU fund and company money and says 98% of the affected token assets were replenished by October 31, visible on its Proof of Reserves page. These are Binance's own statements, with no independent audit behind them.

Withdrawals reopened in phases from November 1, Bitcoin and Ethereum first, and more than $3.6B was withdrawn on the first day.

How AI Is Lowering the Attack Barrier

Binance's own report puts AI tools on the attack path. The breach began with a fake installer for an AI coding tool, and the attackers moved through an internal AI tool. AI did not sign the theft, and no vendor quantifies an AI share of hack losses. AI measurably scales scams.

Binance's November 3 findings are the first primary source to put AI on a record theft's path, in two places. The first foothold came when an engineer searched for a popular AI coding tool and installed a tampered Homebrew package, and on October 20 the attackers used Binance's own internal AI tool to reach two more engineers. Neither step signed the theft. AI tooling was simply a trusted surface the attackers could move through, much like the fake job interview. Before this report, TRM, Fireblocks and the Aave forum thread named no AI role.

Chainalysis found AI-enabled scam operations extracting $3.2M each, against $719K without AI, about 4.5 times more profitable. TRM's AI-in-crime index climbed to 54 of 100 from about 28 in 2024, with scams the only category it rates Mature. Impersonation scams rose about 1,400% year over year in Chainalysis's scam data, a trend we break down in our impersonation-scam piece.

Named AI-agent losses stayed small. Blockaid traced Bankr's about $216K loss to a prompt injection in May, and CertiK ties Zerion's $100K to DPRK-linked AI social engineering; those are the only dollar-quantified AI-agent thefts.

The biggest 2026 hack at an AI project ran through compromised keys, not AI. The September ASI Alliance mint created about 2.3B unauthorized FET through compromised keys, with no burn or re-backing confirmed as of November 3, and part of it was cashed for about 523 ETH, per Bitquery's trace.

If you let an AI agent such as Bankr spend from your wallet, that permission is a delegation of the same kind that drained Binance, so the EIP-7702 check in the last section applies to it. DropsTab's free x402 ecosystem and AI agents categories list the agents that handle funds through the x402 payment standard.

AI made 2026's scams more profitable, and in the record theft, AI tools were part of the path to stolen signing access. The longer-horizon threat to those same keys is quantum computing, which we cover in quantum-resistant crypto.

What Happens to the Token After a Hack

A CEX breach leaves the token's supply untouched, and BNB's total still equals its 131.5M cap. A mint hack is a supply event. Its outcome depends on burning, re-backing, reissue or migration, and on whether anyone could freeze the minted tokens.

A mint exploit creates supply that either gets unwound or hangs over the market, and October added two cases, Cysic and Initia. The table tracks every 2026 mint we verified, with supply outcomes and no prices; BNB is not in it, because a CEX theft only moves balances.

A bug in Initia's smart-contract engine, exploited on launch day, let the attacker mint 2M bridged AUSD on October 23 and cash out about $2.7M, and Agora says it has no AUSD contracts on Initia so the issuer could freeze nothing.

On uncapped tokens, compare against a dated supply snapshot. About 4B ONE were minted in August, about 26% of supply at the time by Harmony's figures, which the Harmony coin page lets you check; Syscoin burned its mint.

Drift sits outside the table by design. It lost about $285M to fake collateral, and no DRIFT was minted.

Immunefi tracked 82 hacked tokens across 2024–2025 and found about 84% below their pre-hack price six months later, a median 61% drop. When a firm collapses with the money inside, our crypto bankruptcies tracker follows what creditors recover.

KelpDAO's rsETH closed its recovery plan with a final tranche of 20,373.72 rsETH, and the token has been fully backed since the unpause.

On privacy chains, supply integrity can be impossible to verify at all, as Zcash holders learned between 2022 and 2026, which we cover in Zcash vs Bitcoin.

The Biggest Crypto Hacks of 2026 and Their Attack Vectors

Four of 2026's five largest thefts needed no smart-contract bug. Binance, Bitget, KelpDAO and Drift each ran through keys, signing or a social-engineered operator. Liquid Network's code flaw is the one large exception.

Ranked by loss, Binance leads Bybit's previous record by more than four to one, and every other 2026 theft stayed below Ronin's 2022 haul of $625M.

Across every year since 2010, the DropsTab team counts more than 1,200 hacked projects and about $27.6B stolen, and maps the largest of them in one chart.

Almost all of crypto got hacked at least once. 1,200+ projects. $27.6B stolen.

Bitget is the year's other exchange hack, five weeks before Binance, and its size stays contested. CEO Gracy Chen put the September 24 theft at $351.6M, Halborn and CertiK at $387.5M and ZachXBT at $388M. Halborn traced the entry to a flaw in a third-party security product that exposed internal credentials.

ZachXBT later connected the two thefts on-chain.

Update: Stolen funds from the $6.3B Binance exploit and $388M Bitget exploit were commingled at the same address 45 minutes ago, after arriving via THORChain. This indicates the same actor is likely behind both incidents.

Liquid is the one large 2026 loss caused by a code bug. Blockstream's post-mortem describes a range-proof caching bug in the Elements software that minted about 4,000 unbacked L-BTC with no key compromised. Self-declared white hats returned 3,400 BTC after negotiations, with about 602 BTC still outstanding.

KelpDAO's bridge trusted a single LayerZero verifier, a 1-of-1 DVN, and the attackers fed it false data. Drift's attackers pre-signed an admin handover that Solana let them execute later. Neither break lived in contract code.

Tectonic, a lending protocol on Cronos, was drained through its collateral. On August 30 the attacker inflated the price of the thinly traded TONIC token, posted it as collateral and borrowed $120.4M across nine markets, according to the Cronos post-mortem. The chain itself then reversed most of the loss.

Aave founder Stani Kulechov broke down how the KelpDAO exploit left the lending protocol carrying roughly $200M in bad debt:

Bybit's about $1.5B hack of February 2025 held the record until Binance. Its US lawsuit won a preliminary injunction in August 2026, with $48.4M retrieved and $30.5M frozen, still largely symbolic against a sovereign attacker.

A Hack's Blast Radius Beyond the Token

The total held in Binance's publicly known wallets, by DefiLlama's count, fell 24.5% in the week after the breach. That drop is about $41.6B, and most of it exceeds the market-wide move. A mega-heist's larger damage is the run and rotation it triggers, beyond the stolen sum.

We pulled DefiLlama's TVL of publicly known wallets on November 3. Against a −4.4% peer baseline, the Bybit and Robinhood average, about 20.1 points of Binance's drop, roughly $34B, is its own, and the theft explains only about 3.8 points. Part of the excess can be BNB's price.

OKX gained 59.8%, about $10.8B, roughly a quarter of what left Binance, in a week when the market fell.

Aave was hit by both 2026 mega-heists. After KelpDAO in April it carried the bad debt and its TVL fell from about $26.4B to $14.3B in six days; in October its emergency multisig froze 292 markets within hours.

Tether occupies both ends of the freeze story, as authority and as investor. Its DropsTab investor profile lists 41 portfolio coins, and only Drift, possibly LayerZero, ties to this year's exploits.

DropsTab's funding records show Drift raised about $52M from Multicoin, Polychain, Jump and Alameda, lost about $285M, and then needed a rescue credit from Tether, the company that froze Binance's stolen USDT. Our records carry about $145M for it; about $147.5M was reported at the recovery token's launch.

Tracking a Hacked Token's Supply and Delisting on DropsTab

DropsTab's Hacked & Exploited Tokens tab puts a hacked token's supply, CertiK score and exchange count side by side, Drops Bot alerts show where the unfrozen part of a haul moves, and the Lazarus portfolio records DPRK-attributed hauls. None brings the money back, and all three are free.

Three free tools let you keep watch after a hack.

Check supply and venues in the Hacked & Exploited Tokens tab. The DropsTab Research tab lists the tokens still trading after a 2026 exploit, with circulating supply and its share of the total, exchange count and CertiK score, free to sort or clone in Tab Builder. Compare the supply with a pre-hack figure, since a mint changes it and a venue breach does not. In the current tab, SAND and FET hold AA CertiK grades, DRIFT sits at BBB, CYS at BB, and WEMIX has no CertiK coverage.

Watch published attacker addresses with Drops Bot. Drops Bot tracks any public address in Telegram, 20 wallets on the free plan across 30 networks including Tron, with IN and OUT direction filters, value filters, custom labels and no private keys. The wallet-alert setup guide walks the configuration. Use only addresses published by the FBI, TRM, Chainalysis or Binance. Our crypto whale tracking guide covers checking who owns a wallet, and lists go stale fast.

Follow the Lazarus portfolio. The Lazarus tracker records the group's attributed hauls from earlier thefts, led by Bybit. The Binance attacker addresses are listed in the FBI's October 31 alert, and wallet alerts on them are how to watch the Binance haul move.

Check your own EIP-7702 delegations

The Binance breach reused an attack that already hits retail wallets. EIP-7702, live since Ethereum's Pectra upgrade on May 7, 2025, lets one signature delegate a wallet's code to a contract. The delegation persists until it is reset to the zero address, and a delegation signed without naming a specific chain works on every Ethereum-compatible chain.

Etherscan's EIP-7702 Authorisation List and Revoke.cash display delegations without touching funds, and Etherscan flags phishing delegates. Revoking happens in the wallet, in MetaMask under Account details and Smart account, per network, and costs gas.

An academic study published on arXiv in December 2025 scanned Ethereum's EIP-7702 authorizations on-chain and counted more than 26,000 victim addresses, with crime-linked delegators holding nearly half of all authorizations, and its largest single victim lost over 3,300 ETH.