Deep research · Fieldnotes

Binance October 2026 theft

Research date: 17 November 2026. A deep OSINT case file on the largest crypto theft on record — what was reported, how the attack unfolded, what it cost, what techniques and indicators were published, and what is still unknown. Figures differ between counters by scope, valuation moment and chain coverage; they are shown side by side, never added together.

Confirmed by multiple independent sources: a drain from Binance hot wallets on 29 October 2026, EIP-7702 delegation abuse, roughly $2.7–2.85bn frozen or blocked, Binance covering losses from company funds, and FBI attribution to North Korea's TraderTraitor on 31 October. Disputed: the attribution itself, and every headline total.

Summary

On 29 October 2026 an attacker drained Binance hot wallets, most of it in about 20 minutes from 20:05 UTC, in what every major tracker calls the largest crypto theft on record — roughly four times the ~$1.5bn Bybit theft of February 2025.

Binance's 3 November initial report traces a months-long campaign: a tampered Homebrew installer in June, a fake job interview and malicious code repository in September, a pivot via an internal AI tool on 20 October, a container deployment with a stolen deployment token on 29 October, abuse of the internal wallet signing service, and direct transfers on most chains plus an EIP-7702 delegation sweep of “Binance 14” on Ethereum.

Binance says no wallet private key leaked; the attacker instead got Binance's own signing infrastructure to sign. That distinction is central, and is corroborated on-chain by TRM, Elliptic, Chainalysis and Blockaid: valid signatures on many chains, and 50 pre-signed EIP-7702 authorisations.

Frozen is not recovered, and recovered is not replenished. Frozen or blocked assets are issuer and network freezes, not money returned to users. Replenishment is Binance buying replacement tokens with company, SAFU and Futures-insurance money. The attacker still held roughly $2.4–3.3bn in unf freezable assets in the 30 October–3 November snapshots, depending on scope and timing.

Reporting timeline

All times UTC unless stated; Binance's 3 November report uses UTC+8, converted here where noted.

  • June 2026 — tampered installer. Engineer A, in wallet development and operations, searched online for a popular AI coding tool and downloaded a tampered Homebrew installer. Binance security detected the anomaly, replaced the device and rotated credentials — but Engineer A's role and wallet-team colleagues had already been exposed. Binance does not name the AI tool, the search term or the installer host.
  • 2026 to date — background. Binance says it detected and prevented 57 suspected North Korea-linked incidents in 2026. Whether any of the 57 is this same campaign is not stated.
  • September 2026 — fake job interview. Software Engineer B, whose profile on a legitimate job platform mentioned Binance work, was contacted by someone impersonating a project director. Round one was a live video interview with a purported HR representative who shared a social-media account with personal photos and videos to build trust. Round two was via a popular messaging app with someone claiming to be the CEO of a fictitious company. Near the end, Engineer B was asked to download an “assignment” code repository onto a work computer; malicious code executed during installation. Neither the platform, the fictitious company, the repository nor any person is named.
  • Malware behaviour (Binance, file operations only — no hash, domain or IP published). Obfuscated, evasion-capable, described as zero-day at the time; it replaced a legitimate development-tool component with a malicious version to execute commands and contact an attacker-controlled server, concealed activity and erased traces. Published operations: CREATE /opt/homebrew/Cellar/pyenv/2.8.0/libexec/pyenv_ (3,414 B), DELETE the legitimate pyenv (3,344 B), RENAME pyenv_ to pyenv, DELETE /opt/homebrew/bin/pyenv, then a new symlink and a spawned zsh.
  • 20 October 2026 — internal AI-tool pivot. Attackers used Engineer B's compromised computer and an internal AI tool to take control of devices belonging to Engineer A and Engineer C, another wallet software engineer, and quickly found a token on Engineer A's computer with container-deployment permissions. The AI tool is not named, and Binance does not describe the AI-tool vulnerability or mechanism.
  • 28 October, morning — on-chain staging. The attacker operator wallet received three small Tornado Cash withdrawals (Elliptic: three × 0.1 ETH). Early on 29 October it deployed and tested code on two wallets, rehearsed the final version on a third, and routed test funds back.
  • 29 October, 15:59 UTC — sweeper deployed. The operator deployed the sweeper contract later used on Binance 14, about four hours before use, after rehearsals moving $2–$6.
  • 29 October, 17:15–19:56 UTC — signing-service infiltration. Attackers logged into Engineer C's computer, deployed a container using credentials stolen from Engineer A, and ran a malicious script to launch the attack.
  • 29 October, 20:05–20:09 UTC — first drain, XRP Ledger. Five Binance hot wallets sent 233.46m XRP to one attacker address, leaving minimum balances; that XRP had not moved in later snapshots.
  • 29 October, shortly after 20:10 UTC — Solana, Optimism (and, per Elliptic, NEAR, Base). Binance: about 970,500 SOL and 44.2m OP to attacker addresses, then an internal alert on large transfers and an investigation.
  • 29 October, 20:20 UTC — Bitcoin, Tron and EIP-7702 delegation. A Binance Bitcoin hot wallet sent 18,270 BTC (peel-chained into roughly 1,000 / 100 BTC pieces in the same block, per TRM); within about two minutes a Tron wallet sent 612.7m USDT + 46.4m TRX. At 20:20:59 UTC the operator sent a type-4 transaction to Binance 14 carrying 50 EIP-7702 authorisations signed with the Binance 14 key, nonces 18,914,775–18,914,824; one matched (ThreatMon: nonce 18,914,809).
  • 29 October, 20:24:23 UTC — the $2.5bn sweep. The operator called sweep on Binance 14: 167,464 ETH, 1.615bn USDT and roughly 60–65 other tokens to collection address 0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c, leaving 1 ETH. Elliptic values the single transaction at about $2.53bn. Within 12 minutes, 10 more Binance hot wallets on four chains sent funds to the same address.
  • 29 October, 20:36 / 20:44 UTC — payouts stop. Last customer payouts on Solana, BNB Chain and Tron at 20:36 UTC, Ethereum at 20:44 UTC. Binance hot-wallet payouts then fell 99.8% over 54 hours.
  • 29 October, 20:41–23:56 UTC — standing drain. Because the delegation persisted, Binance 14 was swept again at 20:41, 20:59, 21:04, 21:44, 22:39 and 23:56 UTC. It also pulled 823m USDC (780m + 43m) from Binance-owned smart account “Hot Wallet 34” via its owner rights at 20:41:23 UTC. The 21:44 sweep alone took 200m USDT + 13 tokens deposited after the first sweep. Binance's own later top-up of Binance 14 was also swept — the mechanism, not just the initial balance, is the lesson.
  • 29 October, about 21:01–22:26 UTC — freezes begin. Tether froze 971.1m USDT in the main wallet at 21:01 UTC; Circle froze 823m USDC at 21:04 UTC; Ripple froze RLUSD at 22:01 UTC; World Liberty Financial froze USD1 at 22:10 / 22:26 UTC. Chainalysis says freezes began by 21:14 UTC — a 13-minute difference from Tether's 21:01 that reflects different “first freeze” definitions, not an average to take.
  • 29 October, 21:29 UTC — first public acknowledgement (secondary reconstruction). Binance said it was aware of reports of a potential security issue; withdrawals suspended.
  • 29 October, 23:05 UTC — second wave. Binance wallets on Avalanche and Polygon (TRM; Elliptic: Avalanche and Polygon shortly after 23:00 UTC).
  • 30 October, 00:10:35 UTC — delegation cleared. Binance used Binance 14 itself to authorise to the zero address (block 26301896), ending the 3h50m delegation window (20:20:59–00:10:35). Final unauthorised transfer: 2,961.9 ETH confirmed at 23:56 UTC on 29 October — it had been broadcast earlier and remained pending.
  • 30 October, 00:13 / 02:25 UTC — Binance first substantive statements. 00:13 UTC: all losses covered, deposits and withdrawals temporarily suspended. 02:25 UTC: about $6.3bn estimated impact, about $3bn frozen, “may involve a compromised DevOps engineer's laptop… access to a service container… unauthorised withdrawal transactions”, “no evidence of any wallet private key leak”, SAFU + company funds to cover, updated proof of reserves promised, detailed post-mortem promised.
  • 30 October — attribution. TRM: TraderTraitor, high confidence (published 02:10 UTC). Chainalysis: TraderTraitor, on commingling with Bitget proceeds (announced 04:30 UTC, published 09:34 UTC).
  • 30 October, 08:47 UTC — Binance widens account. “Additional points of breach”, “complex attack”, attacker “did not simply use one engineer's permissions”, “not a single 'one-click' action” (CEO Richard Teng). Elliptic adds Teng's video claim: the attacker used a self-destruct mechanism destroying tooling and traces, and EIP-7702 delegation “did not pass through our normal approval controls”.
  • 31 October — FBI attribution and 90% replenishment. FBI alert dated 31 October; Binance 31 October update: 90% replenished (up from 80% on 30 October), top-10 tokens 100% backed, new proof-of-reserves snapshot 08:00 UTC+8 on 31 October, zk proof expected 3 November.
  • 31 October — Optimism governance action. Elliptic: Optimism governance appears to have moved 44m OP (about $5m) out of the attacker's address on 31 October. THORChain also paused swaps on 31 October after an Ethereum reorganisation — Chainalysis noted this inadvertently delayed laundering; it was not stated to be a response to the FBI alert.
  • 1 November, 06:00–09:00 UTC (phase 1) — withdrawals resume. Bitcoin first, then selected assets across 15 networks; first 9.5 hours: $4.65bn withdrawals, $1.01bn deposits, net $3.64bn outflow. Binance reported about 95% replenished by 1 November.
  • 2 November — Elliptic laundering update. No evidence AI agents directed laundering; about $3.28bn across more than 950 wallets.
  • 3 November, 04:00 UTC — wider withdrawal reopening. 100+ asset and network pairs across 9 networks (BSC, ETH, SOL, XRP, SUI, ARB, OP, TRX, BASE).
  • 3 November — Binance initial incident report and North Korea denial reported. Binance also says, as of 3 November, it had rebuilt wallet systems and the internal AI tool in fresh environments, replaced devices, disabled credentials and tokens, and completed enhanced scans of all employee devices.
  • 3 November, 13:30 UTC — TRM laundering update. New TRON routes (self-minted token, receipt token, chained bridges); main ETH and BTC balances showed no new relevant activity as of 3 November.
  • 4 November — Recovery Update #7. Binance confirms about 98% of the impacted amount replenished and a new proof-of-reserves snapshot taken at 00:00 UTC on 4 November covering 44 tokens, up from 10 in the 31 October snapshot. The full zero-knowledge proof is expected to take about 50–60 hours, so verification for the wider token list falls around 6–7 November, not 4 November. Withdrawals are still reopening in phases; Update #7 gives no new network list, no completion date, no dollar figure for the remaining ~2% and no identities for the remaining less-liquid tokens.
  • 4 November — Polygon hard-fork proposal to return frozen POL (posted 4 Nov; presented 5 Nov). A Polygon Improvement Proposal, posted 4 November by a Polygon Labs validator-support team member and presented at the Polygon Protocol Governance Call on 5 November (14:30 UTC), asks for a coordinated Polygon PoS hard fork that zeroes the native POL balances of five blocked attacker addresses (about 70.49m POL in total, about US$6.5m) and credits them to Binance's and Polymarket's designated recovery addresses. Binance's share: 46,626,593.27 POL (about $4.3m) in one address — the main collection address 0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c — which also holds 6,185,900.1 USDT already frozen by Tether. If approved, about two weeks to build and test on the Amoy testnet; fork name, activation block and client release still to be decided; no vote outcome posted as of 9 November. The proposal notes the block list is a stopgap, not a complete freeze: a pending transaction offering a fee of about 219,450 POL was seen on 30 October, and the attacker has contacted validators offering cash payment to unblock a transaction. (Posted 4 Nov; not in earlier checks.)
  • 5 November — Recovery Update #8. Third withdrawal batch: withdrawals reopen progressively from 04:00 UTC for assets on six networks — ETH (36 assets, incl. UNI, AAVE, PAXG, VIRTUAL, MORPHO), BSC (24, incl. ASTER, PROM, UNI, 1MBABYDOGE, FIL), Base (AERO, VIRTUAL, MORPHO, AVNT), TRON (JST, SUN, BTTC), Polygon (GNS) and SUI (MMT). Announced 03:04 UTC; prioritised by user demand over the past week; deposits remain open. Update #8 gives no new coverage or proof-of-reserves figures and no completion date for full restoration.
  • 5 November — Binance asks ArbitrumDAO to release frozen ETH + ARB. Binance authored a Constitutional Arbitrum Improvement Proposal, posted to the Arbitrum governance forum on 5 November, asking ArbitrumDAO to approve the release of 8,425.997 ETH and 74,559,805.2 ARB frozen by the Arbitrum Security Council on 29–30 October, to Binance recovery address 0xd9fd39103674cb061d64d9c3b73b878dbe610b80. Worth about $30.7m at 5 November prices (crypto.news). The full process is expected to take around 49 days — one week of forum discussion, one week temperature-check vote, two weeks on-chain vote, then about 18 days to execution — and no new DAO treasury allocation is requested. Returned funds would be applied to incident losses and costs, including replenishing SAFU and treasury reserves. Flag: the proposal discloses that third parties have previously asserted claims to the immobilised assets “on the theory that those assets belong to persons alleged to be responsible for an exploit”, and it will not be submitted on-chain while any restraining notice, writ or order is in effect, unless a court modifies or vacates it. (Posted 5 Nov; not in earlier checks.)
  • 6 November — Recovery Update #9. Fourth withdrawal batch: withdrawals reopen progressively from 04:00 UTC for assets on nine networks — BSC (28 assets, incl. USDE, PENDLE, ZRO, JASMY), Base (7, incl. ZRO, BREV, VIRTUAL, MORPHO), ETH (6, incl. XRP, CAKE, LISTA), Optimism (ETH, ZRO, AXL, WLD), Polygon (ZRO, SAND, AXL, GRT), Arbitrum (PENDLE, ZRO, ETHFI, AXL, GRT), AVAX C-Chain (ZRO, AXL), TRON (U) and SUI (FDUSD). Announced 03:06 UTC; prioritised by user demand over the past week; deposits remain open. Update #9 gives no new coverage or proof-of-reserves figures and no completion date for full restoration — but Binance said it is working to reopen withdrawals for HYPE, INJ, APT, PLASMA, NEAR and LTC by the end of next week, and aims to reopen withdrawals for all tokens on networks already restored (BSC, ETH, Polygon, Arbitrum, Optimism) by then (Binance News summary of the announcement, 03:29 UTC).
  • 6 November — US regulators contact banks. Reuters, reported via Korea Herald Business: supervisors from the US Federal Reserve and the Office of the Comptroller of the Currency began contacting banks on Monday morning (2 November) to ask whether they had detected unusual activity or service disruptions after the hack. No bank reported a disruption; one of the largest US banks contacted Binance’s security team directly within hours of the hack. Supervisory outreach, not an enforcement action.
  • 6 November — Elliptic laundering update (08:45 UTC). First substantive update to the frozen / held / flow picture since 2 November: about $3.11bn still in theft-linked addresses, mostly ETH and BTC, “very likely” still held by North Korea; $2.85bn (44%) frozen or seized; XRP laundering began 5 November — about $50m of ~$276m swapped, mostly via THORChain into BTC, ~$226m still to move; all stolen SOL (~$87m) now swapped, bridged or mixed; about $124m converted into BTC (~1,650 BTC), almost double a day earlier; ~$16m sent to addresses also holding proceeds of the September 2026 Bitget exploit (also attributed to TraderTraitor); ~33 BTC ($2.5m) through Wasabi-style coinjoins since 1 November and ~$1.1m in ETH/SOL into Privacy Cash since 3 November. Scale now 20,000+ wallets, 16 blockchains, 36+ services, 65,000+ transactions. Main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; negligible amount likely cashed out.
  • 6 November — Chainalysis: stolen funds reaching Chinese laundering networks. Chainalysis says hackers are moving some stolen funds through Chinese money-laundering networks, including over-the-counter trading desks — the first confirmed move toward cash-out channels. Only hundreds of thousands of dollars tracked into those networks so far, a small fraction of the total; about $1bn has begun flowing into laundering channels overall; about $500m routed through TRON across 1,000+ addresses; ~$2.42bn in BTC and ETH barely moved (Bloomberg Law, 5 Nov 16:57 UTC; Japan Times and Cryptonomist, 6 Nov). Elliptic’s parallel assessment: funds being laundered “may already be with Chinese money laundering networks”.
  • 6 November — 44-token proof-of-reserves zk proof announced generated. Binance said on Friday that the zero-knowledge proof for the 4 November snapshot (44 tokens) has been generated and users can now verify that their balances are backed at least 1:1 (Decrypt; TechFlow via BlockchainReporter). Flag: BitcoinInsider, published 18:23 SGT, still described the proof as due “around Friday or Saturday” and “once it is published” — likely written before the announcement; and the public proof-of-reserves page as fetched at about 23:00 SGT on 6 November, and re-fetched at about 09:00 SGT on 7 November, still showed blank Audit Time and verification fields, so the proof’s live availability on the page itself was not confirmed in either check. No per-token ratios had been published at the time of either check. (See the 7 November entry: the page’s fields render dynamically and appeared blank on first paint until the cookie prompt was handled, so the earlier blank readings likely reflect the page’s rendering, not an absent proof; the proof may have been live from 6 November.)
  • 7 November — 44-token proof-of-reserves zk proof confirmed live on the public page. Checked at about 23:07 SGT on 7 November: the public proof-of-reserves page now shows the 4 November snapshot complete — Audit Time 04/11/26 00:00:00 UTC (BTC block height 974457), verification mechanism zk-SNARKs, Merkle root hash 12e5018c365c05cbb906372a2b7ae94cc4508cbc8d45031bf932aab46aa98bcd. All 44 tokens show reserve ratios at or above 100%: lowest DOGE at exactly 100.00%, highest FORM at 141.91%; the ten October-31 tokens read BTC 100.03%, ETH 100.02%, USDT 101.55%, BNB 101.49%, SOL 100.13%, USDC 103.12%, XRP 102.13%, USD1 100.96%, ZEC 101.30% and RLUSD 102.89%. This resolves the 6 November entry’s flag — the proof was announced generated on 6 November and the blank fields in earlier checks were most likely a rendering artefact; the page itself gives no publication time for the completed proof, so it cannot be dated to 6 or 7 November from the page alone. A snapshot proves backing at 00:00 UTC on 4 November; it does not audit the theft or verify replenishment purchases beyond the snapshot balances.
  • 7 November — Elliptic laundering update (08:00 UTC). Second substantive update to the frozen / held / flow picture in two days: about $3.13bn still in theft-linked addresses, mostly ETH and BTC, “very likely” still held by North Korea (was ~$3.11bn at 6 Nov 08:45 UTC); $2.85bn (44%) frozen or seized, unchanged (frozen balances rechecked about 07:40 UTC). XRP laundering accelerated — about $100m of ~$276m now swapped, mostly through THORChain into BTC (was ~$50m), about $173m still to move (was ~$226m); overnight, 44m more XRP (~$51m) left the attacker’s addresses. About $175m converted into BTC (~2,300 BTC, was ~1,650 BTC / ~$124m); about $230m of TRX laundered, about $1m now remains; all stolen SOL (~$90m) now swapped, bridged or mixed; only $3m of $1.34bn ETH moved, and $2.5m of $44m NEAR — about 412,000 NEAR ($1.5m) left the main account overnight in small batches. Mixing stepped up: about 77 BTC ($5.8m) through Wasabi-style coinjoins since 1 November (was ~33 BTC / $2.5m), about 88 BTC ($6.7m) mixed in total; about $6.7m in ETH/SOL into Privacy Cash since 3 November (was ~$1.1m) — Privacy Cash paused deposits for about a day from 4 November and its Solana pool resumed the next afternoon. Main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; negligible amount likely cashed out. Elliptic expects the ETH to be swapped for BTC in small transactions and cashed out through OTC brokers over months, and notes laundering is slower so far than after Bybit. Elliptic customers can now screen against nearly 18,000 addresses linked to the theft.
  • 8 November — HYPE and APT withdrawals reopened. Binance's 8 November withdrawal update (“Latest Withdrawal Update”, posted on X) re-enabled withdrawals for Hyperliquid (HYPE) and Aptos (APT) — the first two of the six assets Recovery Update #9 (6 Nov) targeted for reopening by the end of next week (by 13 Nov); INJ, PLASMA, NEAR and LTC still pending. No new Recovery Update (#10) has been published — the announcements page still lists #9 (6 Nov) as latest — and no new proof-of-reserves, frozen or held figures accompany the update. Elliptic's laundering page is also unchanged (last updated 7 Nov 08:00 UTC).
  • 9 November — Binance Alpha withdrawals reopened. Binance's 9 November withdrawal update (posted on X, about 05:03 UTC) re-enabled Alpha withdrawals on four networks — BSC, ETH, Base and Arbitrum — covering dozens of Alpha tokens on ETH and SOL; HYPE and APT are listed as already enabled. No new Recovery Update (#10) has been published — the announcements page still lists #9 (6 Nov) as latest — and no new proof-of-reserves, frozen or held figures accompany the update. Elliptic's laundering page is also unchanged (last updated 7 Nov 08:00 UTC). INJ, PLASMA, NEAR and LTC still pending.
  • 9 November — Elliptic laundering update (data to 13:15 UTC). Third substantive update to the frozen / held / flow picture: about $3.0bn still in theft-linked addresses, mostly ETH and BTC (was ~$3.13bn at 7 Nov 08:00 UTC); $2.85bn (44%) frozen or seized, unchanged. About $225m converted into BTC (~3,000 BTC, was ~$175m / ~2,300 BTC); Wasabi-style coinjoins now about 130 BTC ($10m) in total (was ~88 BTC / $6.7m). New route: from 8 November the attacker began depositing ETH into Tornado Cash — about 7,000 ETH ($15m) by 9 November, about 100 deposits into its 10 ETH pool and about 60 into its 100 ETH pool; some of that ETH came from bitcoin already put through coinjoins and swapped back into ETH through THORChain. XRP laundering continued — about 139m XRP (~$154m) has now left the attacker's addresses, mostly swapped into bitcoin, and about 95m XRP (~$105m) remains (was ~$100m swapped / ~$173m remaining). THORChain halted XRP trading on 7 November; the attacker's swaps resumed from the afternoon of 8 November despite the halt. New technique: about 117,000 NEAR (about $430,000) passed through six home-made meme tokens created 5–7 November, traded through DEX liquidity pools so stolen funds never pass directly between wallets — the same tactic was used after the Bybit hack; Elliptic notes the tokens cost about $90 each to create and the tactic slows tracing rather than hiding the funds. About $220m of TRX has now been laundered, about $0.5m remaining. Main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; negligible amount likely cashed out. Flag: Elliptic's current text puts Privacy Cash at about $1.1m in ETH/SOL since 3 November, against the about $6.7m recorded here for 7 November — the dated narrative shows deposits only on 3–4 November and none since, so the 7 November figure appears to have repeated the coinjoin total; treat the $1.1m as the current figure and the $6.7m as unconfirmed. This supersedes the Alpha entry's “Elliptic unchanged” line above — that note was written before this update appeared. No new Recovery Update (#10) and no new proof-of-reserves figures accompany the update; INJ, PLASMA, NEAR and LTC still pending.
  • 10 November — Elliptic laundering update (data to 11:00 UTC). Fourth substantive update to the frozen / held / flow picture: about $250m converted into BTC (~3,350 BTC, was ~$225m / ~3,000 BTC); Wasabi-style coinjoins now about 150 BTC ($11m) in total (was ~130 BTC / $10m). Tornado Cash now about 11,000 ETH ($24m) since 8 November (was ~7,000 ETH / $15m). XRP laundering accelerated — about 173m XRP (~$190m) now swapped, mostly into bitcoin, and about 60m XRP (~$64m) remains (was ~139m swapped / ~95m remaining), about 33m of it in the last unmoved 2 November address; about 35m more XRP (~$38m) was swapped overnight, and THORChain appeared to halt XRP swaps again on the morning of 10 November, refunding new deposits. All stolen SOL (about $90m) has now been swapped, bridged or mixed; only about 430 SOL remains in linked addresses. Only $3m of $1.25bn ETH and $2m of $42m NEAR have moved. Elliptic customers can now screen against nearly 22,000 addresses linked to the theft (was nearly 18,000). Frozen $2.85bn and held ~$3.0bn unchanged; main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; negligible amount likely cashed out. The ~$16m sent to addresses also holding September 2026 Bitget exploit proceeds, also believed to be TraderTraitor work, is restated in this update — it was already recorded from the 6 November update, not new here. Flag: Elliptic’s 10 November summary puts Privacy Cash at about $6.7m in ETH/SOL on 3–4 November, none since — but the article’s own day-by-day detail still itemises only about $1m (41 ETH and 9,600 SOL on 3 November, about 2,300 SOL more on 4 November), so the $6.7m total is not reconciled inside the article; treat $6.7m as Elliptic’s stated total, not as a verified sum. This supersedes the 9 November entry’s Privacy Cash flag, which treated $1.1m as current and $6.7m as unconfirmed. No new Recovery Update (#10) and no new proof-of-reserves figures accompany the update; INJ, PLASMA, NEAR and LTC still pending.
  • 11 November — Third-party withdrawal check (10:00 Taipei). 620 coin/network pairs on 55 networks open for withdrawals, about 43% of 1,447 pairs — 40 more networks than the 8 November check (400 pairs on 15 networks, about 28%), and up from 361 pairs (about 25%) on 6 November and 236 pairs (about 16%) on 4 November. No new Recovery Update (#10) has been published — the announcements page still lists #9 (6 Nov) as latest — and no new proof-of-reserves figures accompany the check; replenishment was last stated at about 98%. INJ, PLASMA, NEAR and LTC still pending (target about 13 November).
  • 12 November — Binance completes replenishment; new proof of reserves covering 198 tokens. Binance announced on 12 November (16:54 UTC; the announcement page is dated 13 November) that it has completed the replenishment of funds for assets affected by the incident — 100%, up from about 98% in Recovery Update #7 (4 Nov). It committed more than $6.34bn in company funds, bought through market and OTC channels, drawn in part from SAFU, in part from the Binance Futures Insurance Fund above its risk-framework requirements, and in part from corporate treasury; Binance will replenish SAFU back to about $1bn. A new proof-of-reserves snapshot was taken at 00:00 UTC on 12 November covering 198 tokens (was 44); the full zero-knowledge proof is expected in about 40–50 hours, and per-token ratios are now published (BTC 100.05%, ETH 100.02%, USDT 104.34% — secondary reads of Binance’s proof-of-reserves page, Merkle root still in progress; detail under Customer impact and replenishment). Withdrawals continue to reopen in phases, with no statement that all withdrawals are open; INJ, PLASMA, NEAR and LTC — targeted for reopening by about today, 13 November — get no reopening in this announcement. A small number of affected tokens Binance no longer supports will be handled under its delisting process, with holders receiving “appropriate financial protection”. This is not a numbered Recovery Update #10 — it is a differently titled announcement, and the announcements page still lists #9 (6 Nov) as latest. No new frozen, held or flow figures accompany it; Elliptic’s laundering page is unchanged (last updated 10 Nov 11:00 UTC), and the third-party withdrawal tracker has not been re-checked since 11 Nov 10:00 Taipei.
  • 12 November — US DOJ: court-authorized seizure or restraint of more than $1.2bn; collective freeze now more than $2.7bn. The US Department of Justice (press release 26-1356, 12 November) says it has obtained court authorization to seize or restrain more than $1.2 billion in cryptocurrency stolen from Binance, and that collective US government and private-sector efforts have frozen more than $2.7 billion of the stolen funds. The $1.2bn is a subset of the $2.7bn, not additional; seizure or restraint is court-authorized, not completed forfeiture, and the release does not say funds were returned to Binance or customers. The theft is described as “more than $6 billion” on or about 29 October by North Korean military hackers the FBI calls TraderTraitor; tracing, freezing, seizure and forfeiture efforts are ongoing, and the FBI issued a Cyber Alert the previous week attributing the theft and urging VASPs to block TraderTraitor laundering addresses. The same release covers the disruption of cloud infrastructure used in the separate FaceStealer scheme (more than $400m stolen over 18 months; 900+ victim webcam videos seized) — a separate scheme, kept distinct from the Binance theft. No court, judge, coin breakdown or seizure-versus-restraint split is given.
  • 13 November — TRM Labs Beacon Network tracing scale for the Binance theft. TRM Labs launched Beacon Concierge, a managed seizure service for law enforcement, and cited its Beacon Network’s Binance response: more than 26,000 addresses labelled across 14 blockchains, more than 67,000 transfers and links traced including over 1,050 cross-chain swaps, funds followed from 59 origin addresses, an average of 10 hops and as far as 71 hops, and more than 45,000 alerts delivered to participating platforms; 39% of the addresses were flagged by network members and 61% identified automatically. Caveat: Beacon Concierge’s “more than $35m frozen” covers 15 cases for 14 agencies in 10 countries, and “more than $200m interdicted” covers all Beacon Network cases to date — neither figure is Binance-specific and neither is presented as such here. No new Recovery Update; Elliptic’s laundering page is unchanged (last updated 10 Nov 11:00 UTC); the 198-token zero-knowledge proof is not yet published (due about 14–15 November).
  • 14 November — LTC native-network withdrawals reopened (third-party tracker). A live read of the ArbitrageGap withdrawal tracker at 01:01 UTC on 14 November shows Litecoin (LTC) withdrawals open on the Litecoin network (and on BSC); a Crypto Eyes roundup dated 12 November reports the native reopening as “probably since about 14:45 UTC on Wednesday” (11 November) — the date is approximate and no Binance announcement accompanies it, so the reopening is recorded here as tracker-observed, not Binance-confirmed. This supersedes the 8–12 November entries’ “LTC still pending”. NEAR on its native network is still closed (NEAR/BSC open; USDT on NEAR closed); INJ and PLASMA native status was not established in this check. No new Recovery Update; Elliptic’s laundering page is unchanged (last updated 10 Nov 11:00 UTC); the 198-token zero-knowledge proof had still not appeared as of about 01:00 UTC on 14 November (due about 14–15 November).
  • 14 November — Binance reopens withdrawals for 87 networks; third-party tracker jumps to 854 pairs / 94 networks. Binance announcement (14 November) lists 87 networks with withdrawals reopened this week, including APT, HYPE, LTC, NEAR, PLASMA, ADA, AVAX, ATOM, ICP, ALGO and XTZ; Binance says it aims to reopen withdrawals for all remaining networks and assets by the end of next week. This is not a numbered Recovery Update #10 and contains no proof-of-reserves or post-mortem content. Independent check at 10:00 Taipei on 14 November (jason-finance): withdrawals open for 854 pairs on 94 networks, about 59% of 1,447 — up from 620 pairs on 55 networks (about 43%) on 11 November. Flag, do not resolve: Binance lists NEAR and PLASMA among the reopened networks, but an independent network-status read the same morning (Dexsheet) still showed NEAR on its own network paused for maintenance, with HYPE, INJ and XPL open — treat NEAR-native and PLASMA-native as unconfirmed-open, and INJ-native as open. This supersedes the earlier 14 November entry’s “NEAR native still closed” and “INJ/PLASMA not established” lines. 198-token zero-knowledge proof still pending: the Merkle root was still marked as being generated at 10:00 Taipei on 14 November, and the 40–50-hour estimate from the 12 November 00:00 UTC snapshot expired about 02:00 UTC on 14 November; Binance’s 14 November notice says nothing about proof of reserves. (Binance announcement, 14 Nov · jason-finance · Dexsheet)
  • 15 November — 198-token proof-of-reserves zk proof now live on the public page. Verified by direct read of Binance’s proof-of-reserves page at 00:08 SGT on 15 November: Audit Time 12/11/26 00:00:00 UTC (BTC block height 975493), verification mechanism zk-SNARKs, Merkle root hash 05f2f72a91280ef26d3970d94b0c60d7f949aeae5a15bd5f4ddc279987e96cce, and 198 tokens (25 pages, eight per page, six on the last). Binance announced on X on 14 November that the proof had been generated (U.Today; Coinotag; Dave Finances), though no completion announcement appears on its announcements page — the only 14 November announcement there is the withdrawal notice — and the page gives no completion time, so the proof cannot be dated from the page alone; it appeared sometime after the 14 November 10:00 Taipei third-party read still showed the Merkle root being generated and before this 00:08 SGT read. This supersedes the 14 November entry’s “still pending” line and the proof-of-reserves paragraph’s “still being generated” tail. Per-user leaf verification was not tested. (Binance proof of reserves · Coinotag)
  • 16 November — Elliptic laundering update (09:40 UTC). Sixth substantive update to the frozen / held / flow picture: about $2.55bn still in theft-linked addresses (was ~$2.8bn at 13 Nov 07:30 UTC), mostly ETH and BTC, “very likely” still held by North Korea; down about $205m since 13 November, primarily because crypto prices have fallen, not because funds were recovered; $2.85bn (44%) frozen or seized, unchanged (frozen balances rechecked about 09:15 UTC). XRP is now essentially fully swapped — THORChain reopened XRP trading on 13 November and about 7m more XRP was swapped into bitcoin by 14 November, leaving only about 1.3m XRP (~$1m), none swapped since; TRX is almost all swapped too — about $200m through Tron, with less than $2m of each of XRP and TRX remaining. All stolen SOL (about $90m) has now been swapped, bridged or mixed; about $267m converted into bitcoin in total (~4,150 BTC) (was ~4,100 BTC / ~$285m on 12 Nov — the BTC amount rose, the dollar value fell on price). Mixing stepped up: Wasabi-style coinjoins now about 316 BTC ($20m) in total, including about 114 BTC ($7m) over the weekend — “more than in any period so far”; Tornado Cash still about 11,000 ETH since 8 November (was $24m at 10 Nov, now $20m — price fall, same amount); Privacy Cash $6.7m on 3–4 November, none since. Only $3m of $1.07bn ETH and $2m of $37m NEAR have moved. Main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; negligible amount likely cashed out. Scale unchanged: almost 27,000 wallets, 16+ blockchains, 36+ services, 83,000+ transactions. The ~$16m sent to addresses also holding September 2026 Bitget exploit proceeds, also believed to be TraderTraitor work, is restated in this update — it was already recorded from the 6 November update, not new here. Elliptic restates that the laundering shows conventional automation, not AI-agent decision-making — fixed timing, set amounts, blind retries, and pauses that look like human working patterns. No new Recovery Update (#10) and no new proof-of-reserves figures accompany the update. (Elliptic, 16 Nov 09:40 UTC)
  • 16 November — Arbitrum AIP temperature check closed. The Snapshot temperature check on Binance’s Constitutional AIP to release the 8,425.997 ETH + 74,559,805.2 ARB frozen by the Arbitrum Security Council closed on 16 November (vote ran 9–16 November); no final tally had been published at the time of this check, and the next step is a two-week on-chain vote. The funds stay frozen until the on-chain vote passes and the waiting periods run. (AleaResearch governance tracker)
  • 17 November — attacker ETH moves again after weeks quiet. Two separate movements, both reported on 17 November. On-chain analyst Ember (Yu Jin) reported that attacker-linked addresses dispersed 74,881 ETH (about $137m) within about an hour, after most stolen altcoins had been disposed of, with the transferred ETH expected to be split into smaller amounts and routed through cross-chain swap tools; the dispersal was first reported early on 17 November (00:24 UTC). Lookonchain separately reported 74,880 ETH (about $136.8m) transferred out over about three hours and being converted into BTC via THORChain, with the conversion confirmed later the same day (about 10:19 UTC). Separately, MistTrack reported that an attacker address dormant since 30 October transferred 34,279.66 ETH (about $63m) to three newly created addresses (12,000 / 12,000 / 10,279.66 ETH); no ether had moved onward at the time of the report, and the new wallets have no known link to an exchange or laundering service — the transfers alone do not show whether the attackers intend to sell. Flag, do not reconcile: remaining-holdings estimates differ by tracker and address scope — Ember puts the remaining unlaundered holdings at about 18,362 BTC (~$1.19bn) plus 632,000 ETH (~$1.16bn), about $2.35bn combined, while Lookonchain counts 602,402 ETH (~$1.09bn) still held. No new Recovery Update (#10), no new proof-of-reserves snapshot, and Elliptic’s laundering page is unchanged (last updated 16 Nov 09:40 UTC). (CoinDesk, 17 Nov · Lookonchain, 17 Nov · TokenPost, 17 Nov · Blockchain.News, 17 Nov)

Attack path / kill chain

Binance's account unless marked on-chain. Step by step, with the largest gap stated plainly.

  1. Reconnaissance and target selection. The June Homebrew incident exposed Engineer A's wallet-team role and colleagues. Binance does not say how the June installer was distributed in its own report; secondary coverage describing a malicious Google ad is unverified secondary detail, not Binance's wording.
  2. Initial access — two parallel footholds, one successful chain. (a) June tampered Homebrew installer (supply-chain, detected and device replaced — but exposure persisted). (b) September fake-interview repository (social engineering + malicious code execution on install, pyenv replacement, command-and-control contact). Binance presents these as one multi-stage campaign; it does not explicitly state that the June foothold and the September foothold are the same operator's, nor which foothold persisted to October — the October pivot is described from Engineer B's machine.
  3. Persistence and evasion. Malicious pyenv component, obfuscation, trace-erasure, and (per Teng via Elliptic) a self-destruct mechanism. No persistence mechanism beyond this is published; no scheduled task, service or implant name is given.
  4. Lateral movement via internal AI tool (20 October). From Engineer B's machine, via the unnamed internal AI tool, to Engineers A and C. Binance gives no detail on what the AI tool does, what permission it held, or how it was abused — this is the largest technical gap in the published kill chain. Do not fill it with a generic “prompt injection” claim: no source says that.
  5. Credential access and functional privilege escalation (as published). Discovery of a container-deployment token on Engineer A's computer. Binance does not call this privilege escalation, does not say how the token was stored or extracted, and does not publish a separate escalation step. The token plus Engineer C login is the functional escalation: deploy rights, then container, then signing-service access.
  6. Execution and signing-service abuse (29 October, 17:15–19:56 UTC). Login to Engineer C's computer, container deployed with Engineer A's credentials, malicious script run. The attacker then used unauthorised access to the internal wallet signing service to initiate transactions outside the normal withdrawal process. Binance's later wording: EIP-7702 delegation “did not pass through our normal approval controls”.
  7. EIP-7702 persistence (Ethereum). 50 pre-signed authorisations (nonces 18,914,775–18,914,824), one valid delegation, sweeper contract controls Binance 14, repeated sweeps of new deposits without new signatures for 3h50m. MPC design slowed revocation: no single private key could immediately revoke; a specialised revocation process had to be designed and executed.
  8. Cross-chain exfiltration in parallel. Ordinary signed transfers on XRP Ledger, Solana, Optimism, Bitcoin, Tron, Arbitrum, Avalanche, Base, Polygon (and NEAR per Elliptic). TRM's inference, widely repeated: a single actor obtaining valid signatures across chains with different key types and signing schemes points to signing-infrastructure compromise, not per-wallet key theft. Binance's first statement (“no evidence of any wallet private key leak”) is consistent with this.
  9. Laundering — a race against freezes. Conversion was to ETH, BTC and TRX (unfreezable natives) and via DeFi, lending and bridges, at steep discounts (see Impact).
  10. Containment limits. Suspending withdrawals did not stop EIP-7702 transfers already authorised on-chain, nor already-signed cross-chain transfers; only the zero-address re-authorisation (00:10 UTC, 30 October) ended the delegation. Binance says all exploited entry points are now closed and attack-path systems rebuilt or replaced — a claim not yet independently verified (independent review invited, not published).

AI — two different questions, do not conflate them

AI as attack pivot: confirmed as Binance's account — an internal AI tool was used on 20 October to reach Engineers A and C. Tool name, function and abuse method undisclosed.

AI agents as launderers: not evidenced. Elliptic (2 November, via CoinDesk): laundering is automated but looks like human-supervised scripts, not an AI agent making decisions; failed bridge transactions look like script retries, not agent learning; six bridges first used within 100 minutes on 30 October does not establish who or what selected them. Elliptic's main article: “Whether the automation involves AI agents… cannot be determined from the on-chain data.” Elliptic's 9 November update adds that the speed has led to speculation about AI agents, but the evidence points to conventional automation — fixed timing, set amounts, blind retries, new tactics introduced in steps hours apart, and pauses that look like human working patterns; nothing observed shows an AI agent making decisions. Elliptic’s 10 November update restates the same assessment — the laundering is clearly automated, but “nothing we have seen shows an AI agent making decisions” — on the same evidence (fixed timing, set amounts, blind retries, new tactics introduced in steps hours apart, pauses that look like human working patterns).

Impact

Headline totals — different figures, different scopes

CounterTotalScope / valuation
Binance (3 Nov report)~$6.34bn impacted“Digital assets involved”, frozen $2.85bn subject to reconciliation and price moves
Binance (30 Oct statement)~$6.3bnFirst estimate; ~$3bn frozen at that time
TRM Labs~$6.36bn (~$6.23bn at current prices then)10 chains, each transfer at price at moment taken, snapshot 00:30 UTC 30 Oct
Chainalysis~$6.4bnMulti-chain, announced 30 Oct
Elliptic$6.43bn11 chains incl. NEAR; excludes $169m that left Binance after withdrawals suspended, assessed as Binance moving its own funds to long-established addresses
Bitquery$6.3bn17 hot wallets, 9 chains, 20:04–23:56 UTC 29 Oct

By chain and token

  • Ethereum: TRM ~$3.79bn (200,630 ETH + 185 tokens incl. 1.875bn USDT, 823m USDC, 88.5m RLUSD); Elliptic $3.80bn across 186 tokens (1.9bn USDT, 823m USDC). Single sweep ~$2.53bn (Elliptic) / ~$2.5bn (Blockaid). Binance 16 also sent 28,005.6 ETH + 55.7m USDT + 25.9m RLUSD + 84.5 WBTC directly.
  • Bitcoin: 18,270 BTC, TRM ~$1.47bn / Elliptic $1.48bn. Split via peel chain into 19 addresses, mostly 1,000 BTC each (Elliptic); none sent to a service in Elliptic's 1 November snapshot.
  • Tron: TRM ~$628m (612.7m USDT + 46.4m TRX); Elliptic notes 612.7m USDT on Tron. Later: 638m TRX swapped on SunSwap.
  • XRP Ledger: 233.46m XRP, ~$296m (TRM). Unmoved in later snapshots; 233m XRP in a single address per Elliptic 1 November.
  • Solana: 970,500 SOL, ~$96m (TRM / Binance).
  • Arbitrum + Optimism + Base combined: TRM ~$39m (incl. 74.6m ARB on Arbitrum; Arbitrum also 8,426 ETH taken then seized by its Security Council). Optimism: 44.2m OP (Binance).
  • Avalanche: TRM ~$28m (1.81m AVAX + 8.41m USDT per Blockaid, four wallets).
  • Polygon: TRM ~$10m (second wave, 23:05 UTC).
  • NEAR: counted by Elliptic (11th chain) but no separate dollar amount published in the sources read; XRP + SOL + NEAR unmoved together worth ~$439m (Elliptic, 1 November). No NEAR-only figure is invented here.
  • Four assets = 74% of theft (Elliptic): USDT on Ethereum, BTC, USDC, USDT on Tron.
  • Wallets drained: 17 Binance hot wallets (TRM / Bitquery / ThreatMon); Blockaid counts 11 hot-wallet keys sending to the same collection address within 12 minutes of the first sweep plus the delegated wallet — different counting windows, not a contradiction to resolve by picking one. Elliptic traced funds across more than 12,000 wallets on 11 chains.

Frozen, intercepted and attacker-held — snapshot-dependent, do not sum

Counter / dateFrozen / blockedAttacker-held (unfreezable)
TRM, 00:30 UTC 30 Oct~$2.7bn: Tether ~$1.77bn USDT, Circle ~$825m USDC, Ripple 40.5m RLUSD, WLF 27.8m USD1, Arbitrum Security Council 8,426 ETH + 74.6m ARB ~$30m>420,000 ETH + 18,270 BTC, ~$2.4bn
Binance, 30 Oct statement~$3bn frozen on-chain—
Elliptic, ~05:50 UTC 1 Nov$2.85bn verified frozen or seized, 44% of theft, 94% stablecoins (almost all USDT/USDC); Arbitrum + Optimism only chains where everything stolen was secured~$3.25bn across >800 addresses: ~584,000 ETH ($1.32bn), 18,327 BTC ($1.42bn), 233m XRP; XRP/SOL/NEAR ~$439m unmoved
Chainalysis, 11:30 ET 3 Nov~$2.8bn frozen—
Binance, 3 Nov report~$2.85bn frozen or intercepted, subject to reconciliation and price moves—
Bitquery, 09:10 UTC 3 Nov$2.7bn locked (Tether, Circle, Arbitrum + 4 smaller issuers; 6 of Tether's 11 freezes hit already-emptied wallets)~$3.0bn still with attacker, mostly BTC/ETH in wallets that had never sent a transaction; no money identified reaching an exchange deposit address or mixer
Elliptic via CoinDesk, 2 Nov$2.85bn / 44%~$3.28bn across >950 wallets; negligible amount converted to cash
Elliptic, 08:45 UTC 6 Nov$2.85bn frozen or seized, 44% of theft~$3.11bn across theft-linked addresses, mostly ETH/BTC, “very likely” still held by North Korea; negligible amount likely cashed out
Elliptic, 08:00 UTC 7 Nov$2.85bn frozen or seized, 44% of theft (frozen balances rechecked about 07:40 UTC)~$3.13bn across theft-linked addresses, mostly ETH/BTC, “very likely” still held by North Korea; negligible amount likely cashed out; ~$175m converted into BTC (~2,300 BTC), XRP ~$100m of ~$276m swapped
Elliptic, 13:15 UTC 9 Nov$2.85bn frozen or seized, 44% of theft, unchanged~$3.0bn across theft-linked addresses, mostly ETH/BTC, “very likely” still held by North Korea; negligible amount likely cashed out; ~$225m converted into BTC (~3,000 BTC), XRP ~139m (~$154m) swapped, ~95m (~$105m) remaining; Tornado Cash ~7,000 ETH ($15m) since 8 Nov
Elliptic, 11:00 UTC 10 Nov$2.85bn frozen or seized, 44% of theft, unchanged~$3.0bn across theft-linked addresses, mostly ETH/BTC, “very likely” still held by North Korea; negligible amount likely cashed out; ~$250m converted into BTC (~3,350 BTC), XRP ~173m (~$190m) swapped, ~60m (~$64m) remaining; Tornado Cash ~11,000 ETH ($24m) since 8 Nov; all stolen SOL swapped, bridged or mixed, ~430 SOL remains
US DOJ, 12 Nov>$2.7bn frozen (collective US government + private-sector efforts); of that, >$1.2bn under court-authorized seizure or restraint—
Elliptic, 07:30 UTC 13 Nov$2.85bn frozen or seized, 44% of theft, unchanged~$2.8bn across theft-linked addresses, mostly ETH/BTC, “very likely” still held by North Korea; negligible amount likely cashed out; almost all XRP (~$230m) and TRX (~$210m) swapped, mostly into BTC; ~$285m converted into BTC in total; >24,000 addresses screenable
Elliptic, 09:40 UTC 16 Nov$2.85bn frozen or seized, 44% of theft, unchanged~$2.55bn across theft-linked addresses, mostly ETH/BTC, “very likely” still held by North Korea; negligible amount likely cashed out; XRP essentially fully swapped, ~1.3m XRP (~$1m) remaining; TRX almost all swapped, <$2m remaining; ~$267m converted into BTC in total (~4,150 BTC); Wasabi-style coinjoins ~316 BTC ($20m), Tornado Cash ~11,000 ETH ($20m) since 8 Nov

Elliptic, 3 Nov: still in theft-linked addresses ~$3.18bn, vs ~$3.24bn on 2 Nov — valuation-date difference, not a 4 Nov recovery. Elliptic's 2 November attacker-held figure also appears as ~$3.28bn via CoinDesk — intraday snapshot times are not given; do not treat either as superseding the other. Frozen (~$2.85bn) plus held (~$3.18bn) does not sum to any headline total in the sources read; the residual is not itemised. Elliptic, 6 Nov (08:45 UTC): still in theft-linked addresses ~$3.11bn, vs ~$3.18bn on 3 Nov — the first substantive update to the frozen / held picture since 2 Nov; frozen unchanged at $2.85bn (44%). Elliptic, 7 Nov (08:00 UTC): still in theft-linked addresses ~$3.13bn, vs ~$3.11bn on 6 Nov — valuation-date difference and continued conversion into BTC, not a recovery; frozen unchanged at $2.85bn (44%). Elliptic, 9 Nov (data to 13:15 UTC): still in theft-linked addresses ~$3.0bn, vs ~$3.13bn on 7 Nov — continued conversion into BTC and a new Tornado Cash route, not a recovery; frozen unchanged at $2.85bn (44%). Elliptic, 10 Nov (data to 11:00 UTC): still in theft-linked addresses ~$3.0bn, vs ~$3.0bn on 9 Nov — continued conversion into BTC, Tornado Cash now ~11,000 ETH and XRP swaps up to ~173m, not a recovery; frozen unchanged at $2.85bn (44%). Elliptic, 13 Nov (07:30 UTC): still in theft-linked addresses ~$2.8bn, vs ~$3.0bn on 10 Nov — continued conversion into BTC (now ~$285m) and near-complete XRP/TRX swaps, not a recovery; frozen unchanged at $2.85bn (44%). Elliptic, 16 Nov (09:40 UTC): still in theft-linked addresses ~$2.55bn, vs ~$2.8bn on 13 Nov — down about $205m primarily because crypto prices have fallen, not a recovery; frozen unchanged at $2.85bn (44%). US DOJ, 12 Nov: >$2.7bn frozen in total, of which >$1.2bn is court-authorized seizure or restraint — the $1.2bn is a subset of the $2.7bn, not additional; seizure/restraint is not completed forfeiture and no return to Binance or customers is stated.

Other freeze actors (Elliptic): Paxos, First Digital, Tether Gold (XAUT), Binance's own WBETH, issuers of several smaller tokens; Aave froze affected markets (blocked new activity, did not seize funds — the $59.9m USDT / 19,762 ETH Aave position remained open, near liquidation, and is excluded from Elliptic's frozen chart).

Frozen funds now have formal return paths — with conditions, and nothing returned yet. Two governance proposals, both missed by earlier checks, give timelined routes from frozen to returned. Arbitrum: Binance's Constitutional AIP (posted 5 Nov) asks ArbitrumDAO to release 8,425.997 ETH + 74,559,805.2 ARB (about $30.7m) frozen by the Security Council, via a process of about 49 days — but the proposal discloses third-party claims to the assets and will not go on-chain while any restraining process is in effect. Polygon: a Polygon Improvement Proposal (posted 4 Nov, presented 5 Nov) asks for a hard fork returning about 70.49m POL (about US$6.5m) from five blocked addresses, of which Binance's share is 46,626,593.27 POL (about $4.3m); no vote outcome yet, and about two weeks of build and test on Amoy would follow approval. The Polygon proposal's own words: “The funds cannot move, but nothing in the current setup lets them be returned either.” Frozen is still not recovered — these are the first formal paths, not completions. A third formal path arrived on 12 November: the US DOJ obtained court authorization to seize or restrain more than $1.2bn of the stolen crypto, within a collective freeze of more than $2.7bn — seizure or restraint, not completed forfeiture, and no return to Binance or customers is stated. Note the tension, not resolved here: the Polygon proposal marks “no potential party having a right to the funds has contested” as met, while the Arbitrum proposal discloses third-party claims to frozen assets — different chains, but the claims question is not settled.

Conversion losses

About $325m USDT sold via UniswapX / intent contracts for about 122,300 ETH at an implied ~$2,650/ETH vs $2,300–2,350 market (over 10% discount, TRM); Chainalysis: $500m stablecoins moved to a swap wallet, $325m → $285m ETH in about 20 minutes, remaining $175m sent to stopover wallets then frozen. Elliptic: 434m USDT → 160,451 ETH via Uniswap / 1inch / market makers at 12–26% loss; 234m USDT → 638m TRX on SunSwap; 48m RLUSD sold before Ripple freeze; about $786m stablecoins converted to ETH/TRX before freezes. Bitquery: the hacker lost $119m vs market prices on 29–30 October swaps; traders and bots kept $59.9m after costs, builders and validators took $29.5m; Uniswap ETH pools ran up to 38% above market.

Laundering routes (TRM / Chainalysis / Elliptic, 30 October–3 November): market makers and intent contracts, DEXs, Aave / JustLend lending (incl. JustLend receipt-token hops on TRON), SunSwap, Permit2, LI.FI, UniswapX, bridges and swap services (THORChain, Relay, Chainflip, NEAR, CCTP Avalanche → Ethereum for AVAX proceeds → 7,242.8 ETH), self-minted TRON token + liquidity pool, receipt-token transfers that hide USDT links, and chained cross-chain swaps with no intermediate wallet. TRM 3 November: main ETH/BTC balances quiet; active movement on TRON and (from 2 November) Solana. 4 November observations only (movement, not recoveries): Onchain Lens post dated 3 Nov, reported 4 Nov — a hacker-linked address deposited 8,567 SOL (~$798,000) into Privacy Cash; Lookonchain, 4 Nov — hacker-linked wallets continue converting SOL → USDC → bridged ETH → BTC (believed via THORChain), with no transfer sizes or final BTC holdings disclosed; Elliptic (3 Nov, 08:40 UTC) — ~87,000 SOL (~$8m) had left the original Solana theft wallet via new wallets, lending vaults and liquid staking, and ~28 BTC via 18 CoinJoin transactions on 1–2 Nov.

Elliptic, 6 Nov (data to 08:45 UTC): XRP laundering began 5 November — about $50m of ~$276m swapped, mostly through THORChain into BTC, ~$226m still to move; all stolen SOL (~$87m) now swapped, bridged or mixed; about $124m converted into BTC (~1,650 BTC), almost double a day earlier; ~$16m sent to addresses also holding proceeds of the September 2026 Bitget exploit (also attributed to TraderTraitor); ~33 BTC ($2.5m) through Wasabi-style coinjoins since 1 November and ~$1.1m in ETH/SOL into Privacy Cash since 3 November; main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved. Chainalysis (reported 6 Nov): hundreds of thousands of dollars tracked into Chinese money-laundering networks, including OTC desks — the first confirmed move toward cash-out channels; about $1bn has begun flowing into laundering channels overall; about $500m routed through TRON across 1,000+ addresses; ~$2.42bn in BTC/ETH barely moved. Elliptic’s parallel assessment: funds being laundered “may already be with Chinese money laundering networks”.

Elliptic, 7 Nov (data to 08:00 UTC): XRP laundering accelerated overnight — about $100m of ~$276m now swapped (44m more XRP, ~$51m, mostly through THORChain into BTC), about $173m still to move; about $175m converted into BTC (~2,300 BTC); about $230m of TRX laundered with about $1m remaining; all stolen SOL (~$90m) swapped, bridged or mixed; only $3m of $1.34bn ETH and $2.5m of $44m NEAR moved; Wasabi-style coinjoins about 77 BTC ($5.8m) since 1 November, about 88 BTC ($6.7m) mixed in total; about $6.7m in ETH/SOL into Privacy Cash since 3 November (deposits paused for about a day from 4 November, Solana pool resumed the next afternoon); main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; frozen still $2.85bn. Elliptic expects the ETH to be swapped for BTC in small transactions and cashed out through OTC brokers over months; laundering is slower so far than after Bybit, where all 499,000 stolen ETH was swapped within ten days.

Elliptic, 9 Nov (data to 13:15 UTC): XRP laundering continued — about 139m XRP (~$154m) now swapped, mostly through THORChain into bitcoin, about 95m XRP (~$105m) still to move; THORChain halted XRP trading on 7 November and the attacker’s swaps resumed from the afternoon of 8 November despite the halt. About $225m converted into BTC (~3,000 BTC); about $220m of TRX laundered with about $0.5m remaining; Wasabi-style coinjoins about 130 BTC ($10m) in total. New route: from 8 November the attacker deposited about 7,000 ETH ($15m) into Tornado Cash — about 100 deposits into its 10 ETH pool and about 60 into its 100 ETH pool — some of it ETH bought back from coinjoined bitcoin via THORChain. New technique: about 117,000 NEAR (about $430,000) passed through six home-made meme tokens created 5–7 November, traded through DEX liquidity pools; the same tactic was used after the Bybit hack. Flag: Elliptic’s current text puts Privacy Cash at about $1.1m in ETH/SOL since 3 November, against the about $6.7m recorded here for 7 November — the dated narrative shows deposits only on 3–4 November and none since, so the 7 November figure appears to have repeated the coinjoin total; treat the $1.1m as current and the $6.7m as unconfirmed. Main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; frozen still $2.85bn; negligible amount likely cashed out.

Elliptic, 10 Nov (data to 11:00 UTC): XRP laundering accelerated overnight — about 35m more XRP (~$38m) swapped through THORChain, almost all into bitcoin; about 173m XRP (~$190m) now swapped in total, about 60m XRP (~$64m) still to move, about 33m of it in the last unmoved 2 November address; THORChain appeared to halt XRP swaps again on the morning of 10 November, refunding new deposits. About $250m converted into BTC (~3,350 BTC); Wasabi-style coinjoins about 150 BTC ($11m) in total; Tornado Cash about 11,000 ETH ($24m) since 8 November. All stolen SOL (about $90m) swapped, bridged or mixed; only about 430 SOL remains in linked addresses. Flag: Elliptic’s summary now puts Privacy Cash at about $6.7m in ETH/SOL on 3–4 November, none since — but the article’s own day-by-day detail still itemises only about $1m (41 ETH and 9,600 SOL on 3 November, about 2,300 SOL more on 4 November), so the $6.7m total is not reconciled inside the article; treat it as Elliptic’s stated total, not a verified sum. Elliptic customers can now screen against nearly 22,000 addresses linked to the theft (was nearly 18,000). Main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; frozen still $2.85bn; negligible amount likely cashed out.

Elliptic, 13 Nov (data to 07:30 UTC): fifth substantive update to the frozen / held / flow picture: almost 27,000 wallets (was >20,000), >83,000 transactions (was ≥65,000), ~$2.8bn still in theft-linked addresses (was ~$3.0bn), mostly ETH and BTC, “very likely” still held by North Korea; $2.85bn frozen or seized, unchanged. Almost all stolen XRP (~$230m) and TRX (~$210m) now swapped, mostly into bitcoin, with less than $10m of each remaining — by the afternoon of 12 Nov about 51m more XRP (~$53m) had been swapped and only ~8.5m XRP (~$9m) remained; THORChain paused XRP trading again. About $285m converted into BTC in total (was ~$250m / ~3,350 BTC). Coinjoins ~150 BTC ($11m) and Tornado Cash ~11,000 ETH ($24m) unchanged from 10 Nov; Privacy Cash ~$6.7m stated total for 3–4 Nov, none since (restated, not new). Elliptic customers can now screen against more than 24,000 addresses (was nearly 22,000). Main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; negligible amount likely cashed out. Flag: the article’s own day-by-day body still carries the older “more than 20,000 wallets… at least 65,000 transactions” line alongside the updated header figures — the two are not reconciled inside the article; treat the header figures as the update. No new Recovery Update and no new proof-of-reserves figures accompany the update.

Elliptic, 16 Nov (data to 09:40 UTC): sixth substantive update to the frozen / held / flow picture: ~$2.55bn still in theft-linked addresses (was ~$2.8bn), mostly ETH and BTC, “very likely” still held by North Korea; down about $205m since 13 November, primarily because crypto prices have fallen; $2.85bn frozen or seized, unchanged. XRP essentially fully swapped — THORChain reopened XRP trading on 13 November and about 7m more XRP was swapped into bitcoin by 14 November, leaving only about 1.3m XRP (~$1m), none swapped since; TRX almost all swapped — about $200m through Tron, less than $2m of each of XRP and TRX remaining. About $267m converted into bitcoin in total (~4,150 BTC) (was ~4,100 BTC / ~$285m on 12 Nov — the BTC amount rose, the dollar value fell on price). Wasabi-style coinjoins now about 316 BTC ($20m) in total, including about 114 BTC ($7m) over the weekend — more than in any period so far; Tornado Cash still about 11,000 ETH since 8 November (was $24m at 10 Nov, now $20m — price fall, same amount); Privacy Cash $6.7m on 3–4 November, none since. Only $3m of $1.07bn ETH and $2m of $37m NEAR have moved; all stolen SOL (about $90m) swapped, bridged or mixed. Main BTC (18,270) and the nine largest ETH addresses (89% of attacker ETH) still unmoved; negligible amount likely cashed out. The ~$16m sent to addresses also holding September 2026 Bitget exploit proceeds is restated (already recorded from the 6 November update, not new). Elliptic restates that the laundering shows conventional automation, not AI-agent decision-making. No new Recovery Update and no new proof-of-reserves figures accompany the update.

17 November — attacker ETH moves again (on-chain observations, not an Elliptic update): Ember (Yu Jin) reported attacker-linked addresses dispersing 74,881 ETH (about $137m) within about an hour after most stolen altcoins had been disposed of; Lookonchain reported 74,880 ETH (about $136.8m) transferred out over about three hours and being converted into BTC via THORChain. Separately, MistTrack reported an attacker address dormant since 30 October — 0x79e70d139fC05AA75F75611fDF2680E9952B544A — moving 34,279.66 ETH (about $63m) to three newly created addresses in transfers of 12,000, 12,000 and 10,279.66 ETH, with no onward movement at the time of the report and no known link to an exchange or laundering service. Remaining-holdings estimates differ by tracker and address scope (Ember: about 18,362 BTC plus 632,000 ETH, about $2.35bn combined; Lookonchain: 602,402 ETH, about $1.09bn) — do not reconcile them. No new Recovery Update, no new proof-of-reserves snapshot; Elliptic’s laundering page unchanged (last updated 16 Nov 09:40 UTC). (CoinDesk, 17 Nov · Lookonchain, 17 Nov · TokenPost, 17 Nov)

Chainalysis, via the Wall Street Journal (reported 7 November; recorded here as a catch-up): more than $46m in Binance-linked funds passed through THORChain in the first 72 hours after the theft, generating more than $200,000 in fees for node operators, and nearly $4m was mixed through Wasabi Wallet in the same window. The FBI urged THORChain node operators to block theft-linked transactions. Different window and method from Elliptic’s figures above — the $46m is a first-72-hours total across all Binance-linked funds through THORChain, not the XRP-only swap figures; do not add the two together.

Customer impact and replenishment

Binance: “Binance will cover the full amount… not our users”; more than 100% of funds retained to cover losses (3 November report); $5bn already held in the exact impacted token assets at 30 October (Elliptic summary of Binance), rest bought via market / OTC.

Progression as reported: ~80% (30 October) → 90% (31 October) → ~95% (1 November) → 98% of affected token assets as of 31 October (3 November report) → about 98% reaffirmed in Recovery Update #7 (4 November), which Binance's own summary frames as up from 95% → 100% complete, announced 12 November. Flag: the 3 November “98% as of 31 October” still does not sit cleanly against the 31 October update's “90%”; the reports use different phrasing (“affected token assets” vs “affected assets”) and Binance does not explain the gap in the sources read. Do not present 98% as a simple update to 90% without this note. Remaining ~2% (Update #7) = less-liquid tokens, still being purchased via market and OTC channels, with no dollar figure or token identities given (Binance). 98% is replenishment, not recovery: Binance replaced affected assets from company funds; it does not mean 98% of stolen crypto was recovered. 12 November: Binance says replenishment is now complete (100%) — more than $6.34bn in company funds committed, drawn in part from SAFU, in part from the Binance Futures Insurance Fund above its risk-framework requirements, and in part from corporate treasury, with SAFU to be replenished to about $1bn. The same distinction holds at 100%: completion is replenishment, not recovery of stolen crypto.

Funding: SAFU (portion, to be restored to ~$1bn), Futures Insurance Fund (portion above required protection level; Binance says ADL risk not increased, fund remains above required level), corporate treasury. SAFU BTC address published by Binance: 1BAuq7Vho2CEkVkUxbfU26LhwQjbCmWQkD — this is Binance's published SAFU address, not an attacker IOC.

Proof of reserves: snapshot 08:00 UTC+8 on 31 October (Binance Square) / 00:00 UTC on 31 October (secondary summaries — flag the snapshot-time discrepancy; Binance's own 31 October post says 08:00 UTC+8); zk proof 40–50 hours to generate, expected 3 November — delivery not confirmed in sources read to 4 November; a broader snapshot was then taken at 00:00 UTC on 4 November, confirmed in Recovery Update #7, covering 44 tokens, up from 10; its full zero-knowledge proof is expected to take about 50–60 hours, so verification for the wider list falls around 6–7 November; Binance said on Friday 6 November that the proof has been generated and users can now verify ≥1:1 backing (Decrypt; TechFlow via BlockchainReporter) — confirmed live on the public proof-of-reserves page on 7 November at about 23:07 SGT: Audit Time 04/11/26 00:00:00 UTC (BTC block height 974457), verification mechanism zk-SNARKs, Merkle root hash 12e5018c365c05cbb906372a2b7ae94cc4508cbc8d45031bf932aab46aa98bcd, and reserve ratios for all 44 tokens at or above 100% (lowest DOGE 100.00%, highest FORM 141.91%; the ten October-31 tokens: BTC 100.03%, ETH 100.02%, USDT 101.55%, BNB 101.49%, SOL 100.13%, USDC 103.12%, XRP 102.13%, USD1 100.96%, ZEC 101.30%, RLUSD 102.89%). Note the page’s fields render dynamically and appeared blank on first paint until the cookie prompt was handled, so the blank readings in the 6 November (~23:00 SGT) and 7 November (~09:00 SGT) checks likely reflect the page’s rendering, not an absent proof. Ten tokens from the 31 October snapshot independently verifiable at ≥1:1 (BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, ZEC); ratios published in sources read for 6 of the 10 tokens; SOL, USD1, RLUSD and ZEC ratios not given; reported reserve ratios for the 31 October snapshot (secondary, Coin-Turk): BTC 100.04%, ETH 100%, USDT 100%, USDC 106.08%, XRP 100.99%, BNB 101.30%. Futures Insurance Fund is not in proof of reserves. CertiK (via secondary) said it could not yet confirm the $5bn replacement figure for lack of detail — unverified secondary claim, flag as such. A new snapshot was taken at 00:00 UTC on 12 November covering 198 tokens (was 44); the full zero-knowledge proof is expected in about 40–50 hours. Per-token ratios are now published on Binance’s proof-of-reserves page (secondary reads, 12–13 Nov): BTC 100.05%, ETH 100.02%, USDT 104.34%, with the Merkle root still marked in progress — the ratios are Binance’s reported figures, not yet independently verifiable until the proof lands. 14 November: the proof was still being generated (third-party read 10:00 Taipei; Merkle root still marked in progress) — the 40–50-hour estimate from the 12 November 00:00 UTC snapshot expired about 02:00 UTC on 14 November, and Binance’s 14 November withdrawal notice says nothing about proof of reserves. Superseded: verified live on the public page at 00:08 SGT on 15 November — Audit Time 12/11/26 00:00:00 UTC (BTC block height 975493), zk-SNARKs, Merkle root hash 05f2f72a91280ef26d3970d94b0c60d7f949aeae5a15bd5f4ddc279987e96cce, 198 tokens; Binance announced the proof generated on X on 14 November (see timeline), and no completion time is established from the page itself. The Merkle root is now published, completing the proof for the 198-token snapshot; the published per-token ratios (BTC 100.05%, ETH 100.02%, USDT 104.34%) can now be checked against it. User balances in the snapshot (Wu Blockchain comparison via crypto.news): USDT down 928.2m (−3.68%) to 24.3bn over the eight days since 4 Nov; BTC up 0.35% to 687,912; ETH up 1.04% to 3,482,001; BNB up 1.03% to 42,948,718.

Withdrawal suspension: more than 2 days; phased reopening 1 November (15 networks / assets in phase 1), 3 November (100+ pairs), 5 November (third batch: six networks, ETH 36 / BSC 24 / Base 4 / TRON 3 / Polygon 1 / SUI 1 assets) and 6 November (fourth batch: nine networks, BSC 28 / Base 7 / ETH 6 / Optimism 4 / Polygon 4 / Arbitrum 5 / AVAX C-Chain 2 / TRON 1 / SUI 1 assets; Binance also targets HYPE, INJ, APT, PLASMA, NEAR and LTC withdrawals, and all tokens on already-restored networks, by the end of next week); 8 November (HYPE and APT reopened — two of the six targeted assets, ahead of schedule; INJ, PLASMA, NEAR and LTC still pending); 9 November (Binance Alpha withdrawals on BSC, ETH, Base and Arbitrum — dozens of Alpha tokens; HYPE and APT listed as already enabled). Third-party check only, 11 Nov 10:00 Taipei: 620 coin/network pairs on 55 networks open for withdrawals, about 43% of 1,447 pairs — up from 400 pairs (about 28%) on 8 November, 361 pairs (about 25%) on 6 November and 236 pairs (about 16%) on 4 November; a different check from Binance's 15-network phase-1 reopening; do not read as a network closure, and do not present it as Binance's official restoration percentage. No source found in this research reports individual customers losing balances, KYC / personal-data exposure, or a separate compensation scheme — ThreatMon assesses “no evidence of customer data or KYC exposure” on the basis that all reporting covers funds only. That is an absence-of-reporting claim, not a Binance confirmation; flag it. The 12 November Binance announcement gives no reopening for INJ, PLASMA, NEAR or LTC and no completion date; withdrawals continue to reopen in phases. 14 November: Binance announces withdrawals reopened for 87 networks this week (including APT, HYPE, LTC, NEAR and PLASMA) and aims to reopen all remaining networks and assets by the end of next week; third-party check 14 Nov 10:00 Taipei: 854 pairs on 94 networks open, about 59% — up from 620 pairs (about 43%) on 11 Nov. Flag: NEAR-native and PLASMA-native are unconfirmed-open (Binance lists them; an independent status read the same morning still showed NEAR native paused); INJ-native is open per the same read. See the timeline.

Customer outflows after reopening (different windows — do not merge): first 9.5 hours on 1 November: $4.65bn gross withdrawals / $1.01bn deposits / $3.64bn net (2.1% of $171bn assets per Binance / Decrypt). Later Reuters figure: net $4.72bn since reopening, ~3% of platform assets (Reuters, 3 November). Binance co-CEO Teng (reported 4 Nov): from reopening (1 Nov 06:00 UTC) to 4 Nov 04:00 UTC, $10.97bn withdrawn vs $5.695bn deposited = $5.276bn net outflow; final hour deposits ($193m) exceeded withdrawals ($183m). This conflicts in window/definition with the earlier figures — flag, do not average.

Market and sector impact

Immediate prices (Friday 30 October, Reuters via secondary): Bitcoin down nearly 5%, Ethereum down nearly 6%, BNB down nearly 10%. Other windows differ: Bitquery: BNB −5.8% over the halt vs smaller BTC/ETH falls; Reuters Breakingviews (2 November): total crypto market cap down only 2% since the hack (CoinMarketCap), BNB down ~6%. Flag window-dependence; do not quote a single “market fell X%” without its window.

Flows: spot Bitcoin ETFs −$643m on 30 October (largest daily outflow of October, per Reuters via secondary); Ether ETFs −$1.61bn over October (worst month since inception, secondary); more than $1.3bn leveraged liquidations (TRM's Ari Redbord via Reuters secondary). Bitwise via secondary: market adjustment “sharp but orderly”. Reuters Breakingviews: little sign of broader financial-market impact despite crypto–mainstream ties; analysts cited as saying institutional appetite could be curbed.

Competitor flows (Bitquery): Bybit depositors on Ethereum 2.4× usual during the halt; Bitget 2.3× on TRON; Coinbase in normal range; OKX +$284.87m inflows in 24 hours, Gate +$93.22m, Bybit +$29.25m (DeFiLlama via Reuters secondary).

Sector and policy response: South Korea's FSC emergency meeting on 2 November with major exchanges, asking for higher cold-wallet share, 24-hour deposit / withdrawal monitoring and more reserves (Korean law already requires ≥80% cold storage) — secondary. 6 November: US regulators moved to outreach — the Federal Reserve and the Office of the Comptroller of the Currency began contacting banks on 2 November to check for unusual activity or service disruptions after the hack (Reuters via Korea Herald Business); no bank reported a disruption. No sanctions designation, exchange-licence revocation, or regulator enforcement action against Binance has been reported as of 9 November.

TTPs

Only one incident-specific mapping was found, and it is third-party. No official mapping was found in Binance's incident report, the FBI 31 October alert, TRM, Elliptic or Chainalysis in the sources read. Do not invent one from generic TraderTraitor / Lazarus profiles.

TacticTechniqueIncident application (ThreatMon)Caveat
Resource DevelopmentT1587 Develop CapabilitiesSweeper contract written / deployed ~4h early; operator funded via Tornado CashOn-chain
Initial AccessT1566.003 Spearphishing via Service, OR T1195 Supply Chain CompromiseDevOps laptop compromised; method not disclosed at time of writing“Event confirmed, technique assessed”
Lateral MovementT1550 Use Alternate Authentication Material; T1078.004 Cloud AccountsLaptop → service containerBinance statement
ExecutionT1609 Container Administration CommandUnauthorised withdrawal requests from the containerBinance statement
PersistenceT1098 Account Manipulation (closest fit)EIP-7702 delegation writes sweeper into Binance 14's code“ATT&CK has no technique for EIP-7702 delegation abuse; T1098 is the nearest equivalent”
ImpactT1657 Financial Theft~$6.3bn across 10 chains (TRM scope; Elliptic counts 11 incl. NEAR)On-chain

Context only (not Binance-incident mappings): TraderTraitor has no dedicated MITRE group ID; associated groups are Lazarus Group (G0032) and APT38 (G0082). CISA / FBI / Treasury advisory AA22-108A (April 2022) is the general TraderTraitor advisory (fake-job / trojanised crypto apps) — its techniques and IOCs predate Binance by years and must not be presented as Binance IOCs.

IOCs

Only published indicators. The FBI list is a 31 October snapshot (628 addresses). Chainalysis expected tens of thousands of addresses eventually; Elliptic's free blocklist grew from 45 entries (30 October) to more than 8,000 (1 November article) to more than 9,500 customer labels (2 November); Elliptic says customers can screen against more than 24,000 addresses linked to the theft (13 November). TRM’s Beacon Network has labelled more than 26,000 addresses across 14 blockchains in its Binance response (13 November). Any static reproduction here will be stale — screen against the live FBI, Elliptic and TRM feeds, not this page.

FBI list (31 October 2026)

Counts as reported from the FBI page: 608 ETH + 19 BTC + 1 SOL = 628. The FBI page itself says the addresses “are holding or have held assets from the theft, and are operated by or closely connected to” TraderTraitor actors. It is a blocking request to private entities (THORNode / RPC operators, instant exchanges, DeFi, analytics firms, VASPs), not, on the reporting read, a sanctions designation or a return-of-funds order.

First FBI ETH address: 0x8532FA14ACAf483729C449b8458aedDb900543D4 (also ThreatMon's ETH consolidation address, ~195,460 ETH).

FBI SOL address: AffzFDKZbyMiU11zmVBoAqD25ugpr7xoWWyRyGigBEaU.

FBI BTC addresses (verbatim from FBI page tail): bc1qxrxujwxfnvz040jw76d26zhjdg5jura7hs968s, bc1qepc70u3u476vgvg3hfcwjgu4mecxe2uchs4lag, bc1qdfhmlrdvg4tm87zjl0vyf0xflp5ql50q3g88gw, bc1qnq6jj9jmlf3945m3l8s0kxnqehrsga300k8t3s, bc1q42flhayrzy3zh8lkyevw8qcjduurt9a35wlsyx, bc1qz8hdwv8gmml0u96dsvnzsagz6krjyzxmgxupdp, bc1qm2j6v3247khlwzxl7p9vqnfkghcllyhv9wjaat, bc1q0ts8gaf9ht0rr4u02hr56f8thndqsc4kmkmfv3, bc1q2wvz0kcsn4hqmajwtey30ud27fl25w8pveznn6, bc1qalwnl7dtaa73fsq5tyn0ghfy3fgfpqkt69tca8, bc1qjwdw6vrzq4vf6hckutvx4ucj86awwv99mxnz7w, bc1qs3aej5tmcdz0vctz8y9rjcxtxg8v5385577s56, bc1q63qrfrpsg5hh0zzn3kp2xx9vljl7dq7tatsjxp, bc1qs6xnmhar38z44g2za93pv8ygdcwurrh8l87w3v, bc1qg3nrzpuvq2pxqx74tcrywr09dc208ze96n3t53, bc1qf5cyvv9w50tx9xx9s3xwsne0z87wvjj9l8a35u, bc1qm8v88m5fy6kuq9myva2eemwycxqd3e0zcrs2l8, bc1qrg025e2pgx0rwya2kpgtj30972p64jt0hn6zyt, bc1qxg0l4p6xc50zuv9cl5f0l0wmaxjpg8wcy7s9ra.

Do not block Binance's own victim wallets (ThreatMon warning): Binance 14 0x28C6c06298d514Db089934071355E5743bf21d60, Binance 16 0xDFd5293D8e347dFe59E90eFd55b2956a1343963d, Hot Wallet 34 0xEe7aE85f2Fe2239E27D9c1E23fFFe168D63b4055.

Full FBI list: FBI alert, 31 October 2026. Live Elliptic blocklist CSV: Elliptic Binance hack blocklist (CSV) — one address per line, no header or chain label, mostly TRON + EVM, plus BTC, SOL, XRP Ledger.

Key on-chain IOCs

  • Operator: 0x7C8601d4645b93cea45F71e118A729332e6B5CA0 (funded via 3 Tornado Cash withdrawals from 28 October; deployed sweeper; sent type-4 transaction and sweep calls).
  • Sweeper contract (EIP-7702 delegation target, unverified, operator-only caller): 0x63e842B054Bd624a465454D533C33F573e9c6fAe.
  • Main collection address (ETH / OP / ARB / AVAX): 0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c.
  • ETH consolidation (FBI first address): 0x8532FA14ACAf483729C449b8458aedDb900543D4.
  • Tron (Elliptic blocklist via ThreatMon): TPBkSjkCMn2ckrMuAP8n2J1jdjbw76bKN4, TG5iBMQPrDzJJAUM8GMVBf1hRaJ1wvzsGi; XRP (Elliptic blocklist): rK21t6nGLy4MNDqhvy3pGwcLFy25qgfzMx; Solana (Elliptic blocklist, “likely”): AffzFDKZbyMiU11zmVBoAqD25ugpr7xoWWyRyGigBEaU (also FBI SOL), 9SkjwUs5pRRQQo5a6g4m5cciy1xLdDeFnaov24htTjdQ.
  • Transaction hashes (ThreatMon, checked against mainnet by ThreatMon): sweeper deployment 0x97408e7562eb2b28efcd24ba01609607b5749bc89448d007fa8b50ecf290329c (block 26299449); type-4 50-authorisation transaction 0xad99264d5532ae0dd04b2004eebda05f25657e70dacb764f7ac8d4ccd051298b (20:20:59 UTC); first sweep 0x53bd38b816c23e74134786c29a8c18d792777998a3b9326047b583100e88e2f3 (20:24:23 UTC); Binance 16 direct transfer 0x51f263fa50966df6bbd7f8c6e6e99e3791c94444f7c4343b2fef1ee2d62fd39f; Hot Wallet 34 callExecute 780m USDC 0xdc102dd89dded5a83f1008906883ffb7c81ff3b7d7965d8c7277d170b5e17481; second sweep 0x55ba4dabc41b468e580751373ad31acdee6f5ba398682df2c93e5a8340870556 (21:44:11 UTC); revocation 0xafbf94c92a8d749988411669fa14d4f8866d9b4420b4ebd299f28e958dac7209 (00:10:35 UTC, 30 October, block 26301896). Delegation start block 26300753.
  • Behavioural IOCs: EIP-7702 authorisations for one account across a 50-nonce window (18,914,775–18,914,824); code appearing at an EOA that should have none (eth_getCode non-empty); new wallets funded with exactly 0.5 ETH (Elliptic) or receiving exactly 1 TRX before forwarding (Chainalysis); 1,113 TRON transfers from one wallet, median gap 90 seconds, longest pause 39 minutes (Elliptic).
  • Blockaid live tracker: Blockaid Binance hack funds tracker (cited in Blockaid blog; not independently verified live for this research).

Tool, platform and service names

Attacker-used: Tornado Cash (funding), Uniswap, 1inch, UniswapX, Aave, JustLend (TRON), SunSwap, Permit2, LI.FI, THORChain, Relay, Chainflip, NEAR bridge, Circle CCTP, Bitget Wallet Swap Bridge (secondary, via OAK summary), wallet-embedded swap router (TRM, unnamed service), self-minted TRON token + pool (TRM, token unnamed).

Victim-side (Binance, unnamed): internal wallet signing service, internal AI tool, service container, MPC hot wallets. Names not published: AI tool, job platform, fictitious company, code repository, tampered Homebrew host, command-and-control server.

Legitimate tool abused in malware step: pyenv 2.8.0 under Homebrew (/opt/homebrew/Cellar/pyenv/2.8.0/libexec/), zsh.

Freeze and governance actors: Tether, Circle, Ripple, World Liberty Financial, Paxos, First Digital, Arbitrum Security Council, Optimism governance, Aave (market freeze only).

What was not found — do not present as Binance IOCs

No domains, IP addresses, file hashes or malware family names for this incident were published in Binance's report or in the TRM, Elliptic, Chainalysis, Blockaid or FBI sources read. The domains and files in older TraderTraitor coverage (e.g. dafom.dev, tokenais.com, DAFOM-1.0.0.dmg, TokenAIS.app.zip, from CISA AA22-108A STIX, sightings 2018–2022) are historical TraderTraitor IOCs, not Binance-incident IOCs. Likewise, generic TraderTraitor lure domains and IPs in secondary playbooks (e.g. fake Teams / Zoom lures) are not tied to Binance in any primary source read. Any threat-intel page that lists them under “Binance IOCs” without that caveat is conflating campaigns.

Attribution — evidence and dispute

For DPRK / TraderTraitor

  • TRM (30 October, high confidence): robust on- and off-chain intelligence (undisclosed off-chain sources); playbook matches Bybit (February 2025) and KelpDAO (April 2026): small Tornado Cash withdrawals, staging well before theft, pre-obtained signatures in one burst.
  • Chainalysis (30 October, 00:30 ET): strongest evidence = Binance funds commingled on-chain in real time with September Bitget theft proceeds, already attributed to North Korea; plus laundering patterns initially suggesting TraderTraitor.
  • Elliptic (pre-FBI: “likely”; post-FBI: confirms its assessment): (1) Binance funds laundered alongside Bitget proceeds, combined in several wallets (first reported by ZachXBT; Elliptic later: ~$16m sent to addresses holding Bitget proceeds); (2) common service usage with three earlier TraderTraitor-attributed thefts (BigONE, WOO X, AFX); (3) long preparation, staff targeting, abuse of victim's own signing systems resembling Bybit; (4) scale — very few actors could coordinate 11 chains in ~3 hours. Elliptic caveats (important): overlap with Bitget is small; laundering slower than usual for the group; Binance had not published a root cause at that point.
  • ZachXBT / Blockaid / Pangolin Intelligence (secondary): ZachXBT “likely Lazarus”; Pangolin Intelligence also pointed to North Korea. Independent primary posts not re-verified live here.
  • FBI (31 October, formal): “The Democratic People's Republic of Korea (North Korea) was responsible for the theft of more than $6 billion USD in virtual assets from Binance, on or about October 29, 2026. The FBI refers to this specific North Korean malicious cyber activity as 'TraderTraitor'.” With USSS + IRS-CI; observed conversion primarily into ETH, expected further laundering via DeFi and instant swaps; 628 addresses published; report via local field office or ic3.gov. The FBI alert publishes no forensic reasoning, no malware analysis, and no Binance kill-chain detail — its evidential weight rests on the attribution statement + address list, not on published proof.
  • Binance's position: 30 October (via Al Jazeera): CEO Richard Teng — “Our investigation has not attributed responsibility to any individual.” 3 November report: “According to the latest information released by the FBI, the DPRK was responsible” — i.e. Binance cites the FBI; it does not present its own attribution evidence.

Against, dissent and caution

  • North Korea denial (KCNA, reported 3 November): Kim Yo Jong (sister of Kim Jong Un, ruling-party director) denied the FBI announcement, calling it a “grave political provocation” (CoinDesk) / evidence of “US hostile policy” (Reuters), and said there was “no need” for dialogue with Washington. Elliptic rejected the denial, telling CoinDesk its analysis supports the FBI attribution to TraderTraitor.
  • Pre-FBI caution in the record: Vietnam Blockchain Association's ChainTracer (morning 30 October) said identities and locations had not been determined and did not conclude TraderTraitor. A “person familiar with crypto investigations” (via Finance / BigGo, 30 October) cautioned only a handful of groups could execute a theft this size but evidence did not yet conclusively identify Lazarus. ThreatMon (pre-FBI, updated 1 November) rated TraderTraitor “plausible, moderate–high” and noted no government confirmation at that time — now superseded on the government point by the FBI alert, but its caveats about undisclosed off-chain intelligence remain valid.
  • Naming precision: “TraderTraitor” is a US-government activity codename, not a company or org chart; it overlaps vendor names Jade Sleet (Microsoft), UNC4899 (Google / Mandiant), Slow Pisces (Palo Alto Unit 42), and the broader Lazarus umbrella / APT38 / BlueNoroff financial cluster. Equating “TraderTraitor = Lazarus Group” without that note is an oversimplification flagged by multiple secondary analysts. No source in this research names individual operators.

Binance response, remediation and lessons

Immediate response (Binance): internal alert, investigation, withdrawal suspension, emergency controls (freeze coordination with issuers and partners, revocation via zero-address authorisation), law-enforcement + blockchain-intelligence cooperation. Binance says all exploited entry points closed, attack-path systems rebuilt or replaced.

Remediation as of 3 November (Binance): rebuilt affected wallet systems in a fresh environment; rebuilt internal AI tool + strengthened access controls; replaced affected devices; disabled credentials and tokens of affected engineers; enhanced scans of all employee devices; enhanced AI-based behavioural anomaly detection; strengthened wallet-service risk controls.

Next steps (Binance, not yet delivered in sources read): (1) independent third-party cybersecurity review — firms invited, scope and findings to guide remediation, findings to be published in some form (not stated whether the full report will be public); (2) expanded investment in AI security and prevention, endpoint protection, dev-environment security, behavioural anomaly monitoring; (3) security research fund with AI companies, industry participants and security organisations, focused on AI security in blockchain. Some measures will remain confidential (Binance).

Proof-of-reserves status: see Customer impact above. In short: 31 October snapshot published, 10 major tokens ≥1:1 verifiable via zk proof expected 3 November — delivery not confirmed in sources read to 4 November; 4 November snapshot taken 00:00 UTC, 44 tokens, confirmed in Recovery Update #7, with its full zk proof expected in about 50–60 hours (around 6–7 November; Binance said on Friday 6 November the proof has been generated and users can now verify ≥1:1 backing — Decrypt; TechFlow via BlockchainReporter — confirmed live on the public proof-of-reserves page on 7 November at about 23:07 SGT, with Audit Time 04/11/26 00:00:00 UTC, zk-SNARKs, a published Merkle root hash and reserve ratios for all 44 tokens at or above 100%); proof of reserves proves customer-asset backing at snapshot time — it does not prove SAFU / Futures-fund balances (separate pages), does not audit the theft, and does not verify Binance's replenishment purchases beyond the snapshot balances.

Lessons and defensive controls (sourced, not invented)

  • Signer-enforced policy before signing (Blockaid / TRM): destination allowlists, per-transaction and per-window value caps, new-counterparty and mixer-funding checks, and explicit rejection of unexpected EIP-7702 authorisations; a batch of authorisations across a nonce range = IOC. An independent co-signer / policy layer between signing infrastructure and chain (Blockaid's Cosigner model) would have rejected the delegation.
  • Monitor EOA code state (TRM / Blockaid / ThreatMon): alert on any eth_getCode change on a treasury or hot wallet; pre-prepare, pre-approve and rehearse a revocation transaction (zero-address authorisation) — Binance's 3h50m delegation window is the cautionary metric; MPC alone does not solve revocation.
  • Segregate signing by chain and wallet tier (TRM): one compromise must not yield valid signatures on 10 chains (TRM scope); separate approval paths; cap hot-wallet balances to near-term withdrawal need.
  • Separate “can deploy” from “can move money” (TRM / secondary): DevOps laptops and deployment tokens must never be one hop from a signing service; short-lived, hardware-key, audited sessions; no standing path from engineer endpoints to production signers.
  • Endpoint + dev-toolchain hygiene (Binance's own account): verify installer provenance (Homebrew / AI-coding-tool downloads), block running interview “assignments” on work machines, treat fake-recruiter contact via job platforms as a monitored threat (Binance blocked 57 such attempts in 2026 — yet one succeeded), endpoint detection must cover tool-replacement (pyenv swap) not just known malware hashes.
  • AI-tool governance (Binance's remediation): internal AI tools are privileged lateral-movement paths; rebuild + access-control hardening, behavioural anomaly detection on AI-tool use, and treat AI-tool sessions as production access.
  • Freeze-speed and screening (Chainalysis / Elliptic / TRM / Bitquery): rescreen deposits and counterparties against FBI + Elliptic + TRM labels continuously (lists grow from hundreds to thousands in days); follow value through receipt tokens, pool tokens and chained bridges, not just direct transfers; screen several hops downstream, including bridge payouts matched by amount and timing; expect laundering via lending protocols (Aave / JustLend) designed to defeat issuer freezes.
  • BFSI translation: the failure was not broken cryptography or a stolen cold-storage key — it was governance of the approval path. Boards and auditors should test who and what decides what a signer signs, not only where keys live; a reimbursement pledge is not assurance without the independent review, and the proof-of-reserves proof for the 44-token snapshot is now live on the public page (confirmed 7 November, 23:07 SGT), with all 44 tokens at or above 100% — though a reserve snapshot is a point-in-time check, not an audit of the theft or of the replenishment purchases.

Gaps and unknowns

As of 17 November 2026.

  1. Full forensic root cause: Binance's report is explicitly preliminary / initial; independent review invited but not published; some technical details withheld. The “additional points of breach” beyond the laptop (30 October) are never enumerated in the 3 November report.
  2. AI-tool abuse mechanism: tool unnamed, permission model and exploit path undisclosed.
  3. Initial-access details: job platform, fictitious company, recruiter identities, repository name and URL, command-and-control domain and IP, malware family and hash, Homebrew installer host and distribution (malicious-ad claim is secondary-only) — all unpublished.
  4. How signing-service access was obtained from the container: Binance says unauthorised access to the signing service, but not the API, credential or network path, nor whether approval controls were bypassed, misconfigured or absent.
  5. Attribution evidence: FBI publishes no reasoning; TRM's off-chain intelligence is undisclosed; Elliptic's Bitget overlap is small and its caveats stand; no court finding, sanctions designation or named individuals.
  6. Final loss and recovery: totals differ by $130m+ across counters (valuation / scope); frozen totals differ by ~$150m across snapshots; attacker-held totals differ by ~$900m across snapshots; no source reports money actually returned to Binance or customers (frozen ≠ returned), and no seizure or return total is published. Formal return paths now exist for two frozen tranches — the Arbitrum AIP (8,425.997 ETH + 74,559,805.2 ARB, about $30.7m, about 49 days, third-party claims disclosed) and the Polygon PIP (Binance share 46,626,593.27 POL, about $4.3m, no vote outcome yet) — but neither has completed.
  7. Replenishment reconciliation: the 90% (31 October) vs 98% of token assets (as of 31 October, in 3 November report) wording gap; the remaining less-liquid tokens' identities and amounts; SAFU / Futures-fund amounts actually drawn (only “a portion” each); the 4 November proof-of-reserves snapshot’s zk proof is now live on the public page (confirmed 7 November, 23:07 SGT): Audit Time 04/11/26 00:00:00 UTC, zk-SNARKs, Merkle root hash published, all 44 tokens at or above 100% (DOGE 100.00% to FORM 141.91%).
  8. Customer-level impact: no published count of affected users, no per-user loss, no data-breach notification, no regulator findings or enforcement action (supervisory outreach — Fed/OCC bank checks — reported 6 November); “user funds safe” rests on Binance's replenishment claim + proof-of-reserves snapshot, not on an independent audit published to date.
  9. Laundering end-state: negligible cash-out per Elliptic (16 November update, data to 09:40 UTC); ~$2.55bn still in theft-linked addresses (was ~$2.8bn at 13 Nov), down about $205m since 13 November primarily because crypto prices have fallen; XRP essentially fully swapped — only ~1.3m XRP (~$1m) remains, none swapped since, after THORChain reopened XRP trading on 13 November and about 7m more XRP was swapped into bitcoin by 14 November — and TRX almost all swapped, less than $2m of each remaining; ~$267m converted into BTC in total (~4,150 BTC); coinjoins ~316 BTC ($20m) in total, including ~114 BTC ($7m) over the weekend, Privacy Cash ~$6.7m stated total for 3–4 Nov (see the flag in the timeline: the article’s own dated detail itemises only ~$1m, so the $6.7m is not reconciled inside the article; the 13 Nov update restates the $6.7m as its summary total); Tornado Cash ~11,000 ETH ($20m) since 8 November, and home-made meme tokens moving ~117,000 NEAR (~$430,000); about $16m sent to addresses also holding September 2026 Bitget exploit proceeds, also believed to be TraderTraitor work (restated from the 6 November update); all stolen SOL swapped, bridged or mixed, ~430 SOL remains; Chainalysis has tracked hundreds of thousands of dollars into Chinese money-laundering networks including OTC desks, the first confirmed move toward cash-out; where the remaining ~$2.55bn goes is unobserved; on 17 November some of it moved — attacker-linked addresses dispersed about 74,881 ETH (~$137m) within about an hour and a dormant-since-30-October address moved 34,279.66 ETH (~$63m) to three new wallets, with conversion into BTC via THORChain reported — but the end destination is still unobserved (see timeline); THORChain halted XRP trading on 7 November, the attacker’s swaps resumed on 8 November despite the halt, THORChain appeared to halt XRP swaps again on the morning of 10 November, refunding new deposits, paused XRP trading again by the afternoon of 12 November, and reopened it on 13 November. Flag: Elliptic’s own day-by-day body still carries the older “more than 20,000 wallets… at least 65,000 transactions” line against the updated header figures of almost 27,000 wallets and >83,000 transactions.
  10. Still pending at 17 November: independent review — Binance's 3 Nov report says it is engaging independent security firms, but no firm was named and no independent report was published in sources found to 17 Nov; no new attribution on 4–17 November (standing positions: FBI TraderTraitor attribution 31 Oct; North Korea denial reported 3 Nov); final post-mortem not published; full withdrawal restoration: Binance announced 87 networks reopened on 14 Nov and aims to reopen all remaining networks and assets by the end of next week; third-party check 14 Nov 10:00 Taipei: 854 pairs on 94 networks, about 59%; NEAR-native and PLASMA-native unconfirmed-open (see timeline); 198-token proof-of-reserves zk proof: still pending at 14 November (Merkle root still being generated at 10:00 Taipei 14 Nov) — now live, verified on the public page at 00:08 SGT on 15 November (Audit Time 12/11/26 00:00:00 UTC, Merkle root published; Binance announced the proof generated on X on 14 Nov; see timeline); 44-token proof-of-reserves zk proof announced generated on 6 November (Binance, via Decrypt and TechFlow via BlockchainReporter) and confirmed live on the public proof-of-reserves page on 7 November (23:07 SGT), with per-token ratios published for all 44 tokens (all at or above 100%). Arbitrum AIP temperature check closed on 16 November, final tally not yet published at the time of this check, next step a two-week on-chain vote; Polygon PIP still no vote or date.

Sources

Research date 17 November 2026. This page is a deep-research case file, not a daily briefing; figures are as published by the sources above and differ by counter, valuation moment and chain scope. The FBI and Elliptic address lists are live and growing — screen against them, not against a static copy. Previous deep-research pages and daily briefings are untouched.

← Back to main page