T
iTokenly

Binance hot wallets (October 2026) hack — October 2026

Verified — 8 sourcesLast checked October 31, 2026

Incident facts

Date of incident
Publicly disclosedOctober 29, 2026
Target typeCentralised exchange
Loss$6,360,000,000Published estimates range $6,300,000,000 to $6,430,000,000Price at time of incident
Recovered$2,850,000,000
MethodInfrastructure compromiseAn attacker inside Binance’s environment got its hot-wallet signing systems to authorise transfers on ten or more chains, including 50 pre-signed EIP-7702 delegations that handed the Ethereum hot wallet Binance 14 to a sweeper contract. Binance says it has found no evidence of a private-key leak; full root cause not yet published
ChainsEthereum, Bitcoin, Tron, XRP Ledger, Solana, Arbitrum, Optimism, Base, Avalanche, Polygon, Other
Attributed toNorth Korea (TraderTraitor)Alleged
OutcomePartially recovered

What happened

Starting at about 20:05 UTC on 29 October 2026, wallets belonging to Binance sent their balances to attacker-controlled addresses, in the largest crypto theft on record. TRM Labs traced $6.36 billion on ten blockchains at the price of each asset when it was taken. Elliptic counts $6.43 billion on 11 chains, adding NEAR, and leaves out a further $169 million that left after withdrawals were suspended and appears to be Binance moving its own funds. Binance puts the loss at about $6.3 billion. By TRM’s count Ethereum accounts for about $3.79 billion, including 200,630 ETH, 1.875 billion USDT and 823 million USDC; Bitcoin for 18,270 BTC, about $1.47 billion; Tron for about $628 million; the XRP Ledger for 233.46 million XRP, about $296 million; and Solana for about $96 million.

The attacker’s operator wallet received three 0.1 ETH withdrawals from Tornado Cash from 28 October and rehearsed a sweeper contract on other wallets. At 20:20 UTC it submitted one transaction carrying 50 EIP-7702 authorisations signed by the hot wallet Binance 14, one for each upcoming nonce, so that one would match when the transaction landed. About three and a half minutes later the sweeper emptied the wallet of 167,464 ETH and 63 tokens, including 1.6 billion USDT. The delegation stayed in place, so funds arriving later were swept too, the last time at 23:56 UTC, and the wallet’s owner rights over another Binance wallet yielded the 823 million USDC. On the other chains Binance wallets sent funds in ordinary signed transfers. TRM and Elliptic both read that as access to Binance’s signing systems rather than stolen keys.

Binance first said the incident may have started with a compromised DevOps engineer’s laptop that gave access to a service container, then said it had found additional points of breach and no evidence of a private-key leak. Co-CEO Richard Teng said the delegation did not pass through normal approval controls and that a self-destruct mechanism destroyed tooling and traces. Binance had not published its post-mortem when this was recorded.

Tether froze 971.1 million USDT in the main receiving wallet at 21:01 UTC and Circle froze the 823 million USDC three minutes later. Ripple, World Liberty Financial, Paxos and First Digital froze further stablecoins, Arbitrum’s Security Council moved 8,426 ETH and 74.6 million ARB out of the attacker’s reach, and Elliptic says Optimism’s governance appears to have moved 44 million OP on 31 October. Elliptic has verified $2.85 billion frozen or seized on-chain as of about 04:30 UTC on 31 October; Binance’s own figure is about $3 billion. The recovered figure here is Elliptic’s, under this registry’s method, and those funds have not yet been returned to Binance. Elliptic says the attacker still controls about $3.21 billion that no issuer can freeze, including 519,104 ETH, the 18,270 BTC and 233 million XRP.

TRM attributes the theft to North Korea’s TraderTraitor with high confidence, and Chainalysis’s chief executive and Elliptic call that likely; Elliptic confirmed some funds were laundered alongside proceeds of the September 2026 Bitget exploit, as ZachXBT first reported. No government has confirmed the attribution and Binance has not named anyone. Binance says it will cover all losses from its SAFU fund and corporate treasury and has set aside more than $6.34 billion, $5 billion of it in the affected tokens. Teng said only Binance’s own hot wallet was hit; CoinDesk and Bitquery note that the drained wallets appeared on the proof-of-reserves list backing customer balances. Withdrawals were still suspended when this was recorded, with a proof-of-reserves report promised by 2 November.

Sources

  1. Binance on X: initial findings and $6.3bn estimate (30 October 2026)Primary · retrieved 2026-10-31
  2. Binance, Security Incident Update #2 (30 October 2026)Primary · retrieved 2026-10-31
  3. Richard Teng on X: video transcript (30 October 2026)Primary · retrieved 2026-10-31
  4. TRM Labs (29 October 2026)Secondary · retrieved 2026-10-31
  5. Elliptic (updated 31 October 2026)Secondary · retrieved 2026-10-31
  6. Bitquery investigation (October 2026)Secondary · retrieved 2026-10-31
  7. CoinDesk (30 October 2026)Secondary · retrieved 2026-10-31
  8. Cointelegraph live coverage, via TradingView (30 October 2026)Secondary · retrieved 2026-10-31

Changes to this entry

  • Recorded two days after the theft at TRM’s itemised $6.36bn; Binance’s ~$6.3bn and Elliptic’s $6.43bn are the ends of the range. Recovered is Elliptic’s on-chain $2.85bn, below Binance’s rounded ~$3bn. Provisional: move to users-reimbursed once withdrawals reopen and the proof of reserves is published, and revisit the vector when the post-mortem appears.

Cite this

This data is published under CC BY 4.0. You may reuse it, including commercially, as long as you credit iTokenly and link back.

iTokenly Hack Registry, "Binance hot wallets (October 2026) hack — October 2026", iTokenly, accessed 2026-10-31, https://itokenly.com/hacks/binance-hot-wallets-october-2026
https://itokenly.com/hacks/binance-hot-wallets-october-2026

Permalinks never change. If an entry is renamed, the old address keeps working.

Spotted an error? Write to [email protected]. Corrections to published figures are logged on this page. See the methodology for how entries are checked.