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.
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.
All times UTC unless stated; Binance's 3 November report uses UTC+8, converted here where noted.
Binance's account unless marked on-chain. Step by step, with the largest gap stated plainly.
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).
| Counter | Total | Scope / 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.3bn | First 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.4bn | Multi-chain, announced 30 Oct |
| Elliptic | $6.43bn | 11 chains incl. NEAR; excludes $169m that left Binance after withdrawals suspended, assessed as Binance moving its own funds to long-established addresses |
| Bitquery | $6.3bn | 17 hot wallets, 9 chains, 20:04–23:56 UTC 29 Oct |
| Counter / date | Frozen / blocked | Attacker-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.
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.
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.
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.
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.
| Tactic | Technique | Incident application (ThreatMon) | Caveat |
|---|---|---|---|
| Resource Development | T1587 Develop Capabilities | Sweeper contract written / deployed ~4h early; operator funded via Tornado Cash | On-chain |
| Initial Access | T1566.003 Spearphishing via Service, OR T1195 Supply Chain Compromise | DevOps laptop compromised; method not disclosed at time of writing | “Event confirmed, technique assessed” |
| Lateral Movement | T1550 Use Alternate Authentication Material; T1078.004 Cloud Accounts | Laptop → service container | Binance statement |
| Execution | T1609 Container Administration Command | Unauthorised withdrawal requests from the container | Binance statement |
| Persistence | T1098 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” |
| Impact | T1657 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.
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.
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.
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).
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.
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.
As of 17 November 2026.
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.