At 20:05 UTC on 29 October 2026, Binance hot wallets on the XRP Ledger started sending funds to an address the exchange did not control. Over the next four hours wallets on ten blockchains followed - eleven by Elliptic's count - and roughly USD 6.36 billion left the exchange, most of it in the first twenty minutes. It is the largest theft of cryptocurrency on record, about four times the USD 1.5 billion taken from Bybit in February 2025. On 31 October the FBI attributed it to TraderTraitor, the North Korean unit it also blamed for Bybit.

Two details matter more than the size. The blockchain evidence points to no stolen private key: Binance's own signing system appears to have signed what the attacker asked it to. And of everything taken, the part that came back was almost entirely the part with an issuer who could freeze it.

[INFO]
Primary sources: TRM Labs' analysis (30 October, figures as of 00:30 UTC); Elliptic's two posts (30 October with updates to 1 November, and 31 October on laundering); Binance's statements and the FBI's 31 October alert as reported by BleepingComputer. Binance has not published a root cause. Where the sources' figures differ, the article gives each.
[INFO]
Update, 12 November 2026. On 3 November Binance published its initial findings, and they answer the question this article left open: how the attacker reached the signer. The chain ran through three engineers' computers over five months - a tampered Homebrew install in June, a fake job interview in September that swapped a pyenv component, an internal AI tool on 20 October, and a container deployed with a stolen token on 29 October. Binance also gives about USD 2.85 billion frozen or intercepted, and says it had replaced 98% of the affected tokens from its own funds by 31 October. Details in the new section below. The demo now follows the intrusion on the engineers' machines.
◈ interactive artifact
Three Laptops, One Signer
Six stages from Binance's own report, on the machines where they happened: the June search result, the September interview and pyenv swap, the internal AI tool, the 29 October container, the hot wallets draining in UTC, and what came back. Turn on the analyst notes to see what is sourced and what is staged.

//What Binance Has Said

On 30 October Binance linked the theft to a compromised DevOps engineer's laptop, through which the attacker reached a service container and submitted unauthorised withdrawal transactions. It said it had found no evidence that a wallet private key leaked. Co-CEO Richard Teng then widened that: "the attacker did not simply use one engineer's permissions", Binance had "uncovered additional points of breach", and the investigation "has not attributed responsibility to any individual". Binance suspended deposits and withdrawals, revoked the affected address's authorisations, and said it would cover every loss from its SAFU fund and company money. Withdrawals began reopening on 1 November.

//Update: How They Reached the Signer

Binance's 3 November report, "Initial Findings and Response Update", sets out the chain in four stages. It calls the findings preliminary and says some technical details will stay confidential.

June: a search result. Engineer A, on the Wallet DevOps team, "downloaded a tampered Homebrew installation in order to install a popular AI coding tool after searching for it on a search engine". Binance's security team detected the anomaly, replaced the device and rotated A's credentials. Binance says A's role and colleagues on the wallet infrastructure team were exposed all the same. It names neither the tool nor the search engine, and nothing in the report says the Homebrew project itself was compromised.

September: a job interview. Software Engineer B was approached on "a legitimate job-hunting platform by an individual posing as a Project Director". The first interview was a video call with a purported HR person, who shared a social media account full of personal photos to build trust. The second was in a popular chat app with the "CEO" of a company that does not exist, who asked B to download an assignment repository onto the work computer. Setting it up ran obfuscated code that replaced a component of pyenv, the Python version manager, ran commands and contacted an attacker server. Binance lists the file operations: a new /opt/homebrew/Cellar/pyenv/2.8.0/libexec/pyenv_ of 3,414 bytes replaces the 3,344-byte original, and the /opt/homebrew/bin/pyenv link is recreated. "The 0-day malware was not detected by the endpoint security protection tools at the time," and the attacker removed traces. The Ronin bridge theft of 2022 began the same way, with a fake job offer to a senior engineer (see this site's Ronin article). Binance notes that its team had detected and stopped 57 suspected North Korea-linked cases in 2026 before this one.

20 October: an internal AI tool. From B's computer the attacker "used an internal AI tool to gain control over" Engineer A and Wallet Software Engineer C, and found a container deployment permission token on A's computer. Binance does not say how the tool was used.

29 October: a container. Between 17:15 and 19:56 (the report gives no time zone) the attacker logged onto C's computer, used credentials stolen from A to deploy a container, and triggered a script that reached the internal wallet signing service. From there it started transactions outside the normal withdrawal process. On Ethereum it used the signing service for 50 signing transactions that delegated a hot wallet to an attacker contract, which matches TRM's on-chain reading below. The last transfer, 2,961.9 ETH broadcast earlier, finalised at 23:56 UTC. At 00:10 on 30 October Binance signed an authorisation from the Binance14 hot wallet to the zero address, clearing the delegation.

Why it took until 00:10. Pausing withdrawals did not stop the outflow, because the EIP-7702 authorisations lived on-chain and did not go through the withdrawal system. And because the hot wallet uses multi-party computation, "there was no single private key that could be used to immediately revoke the malicious EIP-7702 authorizations". Binance had to build a revocation procedure during the incident.

Replaced is not recovered. Binance says users bear no loss: it set aside more than 100% of the amount and had replenished 98% of the affected tokens by 31 October, buying the less liquid remainder. That is the exchange paying. What came back from the attacker is the roughly USD 2.85 billion frozen or intercepted, the figure Elliptic had already verified, and as the section below shows, almost all of it had an issuer who could freeze it. Binance has rebuilt the wallet system and the internal AI tool, replaced devices, revoked the engineers' credentials, and commissioned an independent review. On attribution it cites the FBI.

//The Signer, Not the Key

TRM's reconstruction explains why "no key leaked" and "billions gone" are both plausible. On nine chains, plus one Ethereum hot wallet, the funds left in ordinary, validly signed transfers. Nothing on-chain distinguishes them from Binance's own withdrawals except the destination. TRM's assessment is that the attacker "likely gained the ability to make Binance's hot wallet signing system sign transactions of its choosing across chains".

The main Ethereum hot wallet went a different way, through EIP-7702. Introduced in Ethereum's Pectra upgrade in May 2025, it lets an ordinary account sign an authorisation that delegates its behaviour to a smart contract; the delegation stays until the account signs another. Teng was reported by the BBC as calling it a "multi-signature protocol". It is not; it is a way for one key to hand its account's behaviour to code. The attacker held 50 such authorisations, each signed by the Binance hot wallet's key, each pointing at a sweeper contract that takes orders only from the attacker's operator wallet.

Why 50? Each EIP-7702 authorisation carries a nonce, the account's transaction counter, and is only valid while the counter has exactly that value. A busy hot wallet's counter keeps moving. The attacker had signatures for 50 consecutive values so that one would still be valid when the moment came. At 20:20 UTC the operator submitted all 50 in one transaction; 3 minutes 24 seconds later the hot wallet's entire balance - 167,464 ETH and 63 tokens including 1.615 billion USDT - was swept. TRM reads the batch as a sign that the attacker could not get signatures whenever it liked: access may have been time-limited, or signatures had to be requested through a system.

None of this was improvised. TRM traces the operator wallet's funding to three small Tornado Cash withdrawals on the morning of 28 October, at least 36 hours earlier. On 29 October the operator tested a first version of the sweeper on two wallets, rehearsed the final one on a third, and installed it on a Binance wallet four hours later. TRM finds the same pattern in Bybit and in April's KelpDAO theft: an operator wallet funded through Tornado Cash, staging well ahead, and signatures obtained beforehand and used in one burst. Bybit also began with one person's machine, a Safe{Wallet} developer's.

//What Came Back Had an Issuer

TRM counted about USD 2.7 billion frozen by 00:30 UTC. Tether froze about 1.77 billion USDT, starting with 971.1 million in the main receiving wallet at 21:01. Circle froze about 825 million USDC, the first 823 million at 21:04. Ripple froze 40.5 million RLUSD, after the attacker had already sold 48 million through decentralised exchanges. World Liberty Financial froze 27.8 million USD1. The Arbitrum Security Council used its forced-transfer power at 00:08 UTC to move 8,426 ETH and 74.6 million ARB out of the attacker's wallet. Elliptic later verified USD 2.85 billion frozen and notes that stablecoins make up 94% of it.

Update, 14 November. On 12 November the Justice Department said it had court authorisation to seize or restrain more than USD 1.2 billion of the stolen funds, part of more than USD 2.7 billion frozen by government and private efforts. It is a seizure and restraint, not yet a forfeiture. The same announcement covered FaceStealer, another North Korean scheme that reaches its targets through trusted conversations; see this site's FaceStealer article.

The 18,270 BTC, about USD 1.47 billion, had no one to ask. TRM saw it split into a peel chain in the same block it arrived. The ETH, XRP, SOL and TRX are the same. The attacker's answer to the stablecoin risk was speed: about 325 million USDT was sold through UniswapX and other intent-based contracts for about 122,300 ETH at a discount of over 10% to market, and 60 million USDT was supplied to Aave to borrow about 19,760 ETH before Aave froze the markets. Paying 10% to turn a freezable dollar into an unfreezable ether is a trade TRM documents; it tells you which assets the attacker regarded as already lost.

The point for anyone holding funds in a hot wallet: the recovery mechanism in this incident was not the exchange's and not the chain's. It was a handful of issuers acting within an hour, and it covered only what they issued. As of TRM's figures the attacker still held about USD 2.4 billion beyond any issuer's reach; Elliptic's later figure is USD 3.25 billion.

//Laundering on Autopilot

Elliptic's second post looks at what happened next on Tron. The main distribution wallet moved funds in every hour for 31 hours, never pausing longer than 46 minutes. Transfers were rarely less than about 30 seconds apart, the roughly 200 wallets it paid usually passed funds on within two minutes, and swaps into THORChain reused the same amounts, one of them 19 times. When a bridge rejected deposits, the funds were rerouted to the same destination through new wallets with no visible pause. Elliptic's reading, which it presents as almost certain rather than proven, is that software was running the laundering; after Bybit, it says, laundering followed human working hours. By 22:41 UTC on 31 October about USD 31 million had gone through THORChain. On 31 October the FBI published 628 addresses - 608 Ethereum, 19 Bitcoin, one Solana - for exchanges to block, and said the stolen funds were being converted mainly into ETH.

//Four Numbers for Everything

How much: USD 6.36 billion (TRM), 6.43 billion (Elliptic), about 6.4 billion (Chainalysis), about 6.3 billion (Binance). The differences are pricing time and which chains are counted.
How many chains: ten (TRM) or eleven (Elliptic).
How long: "about 20 minutes" for most of the value (TRM, from 20:05) and "a few hours" (Elliptic). Both are right: the large transfers came between 20:05 and 20:23, and Ethereum sweeps and the Avalanche and Polygon outflows continued to 23:56.
How much frozen: USD 2.54 billion (Binance, 23:35 UTC on 29 October), about 2.7 billion (TRM), 2.85 billion verified (Elliptic), close to 3 billion (Binance, later). These are snapshots of a moving total, not disagreements.

//What Defenders Can Take From It

This is our reading, not Binance's. It was written before Binance's report and the report bears it out.

A signing service is only as strong as what it agrees to sign. If the evidence holds, the keys were never outside Binance's systems. What failed was the decision about which requests to honour. Policy that checks destination, amount and velocity has to sit with the signer and ignore who is asking, because the attacker in this case was asking from inside.
Some message types should never be signed by a hot wallet. An EIP-7702 authorisation hands an account to code. Fifty of them for consecutive nonces is not a routine request from anything.
The laptop is the perimeter. Bybit, KelpDAO and now Binance began with a person's machine and ended with a valid signature. Binance's report adds the detail: three engineers, a replaced laptop that did not end the targeting, a coding test run on a work computer, and a deploy token sitting on a disk. Engineers with a path to production signing are the target, and their endpoints, their developer toolchains and their job-search inboxes need to be treated that way.
Internal AI tools are part of the path. Binance says the attacker used one to get from one engineer to two others. Any tool that can act across colleagues' machines or accounts needs the same access review as an admin console.

For background on the group, see this site's Lazarus Group article and the history of exchange hacks, which stops before this one.

[IOC]
Date: 29 October 2026, first outflow 20:05 UTC (XRP Ledger); EIP-7702 batch 20:20; main Ethereum sweep 20:23:24; final Ethereum sweep 23:56; Avalanche and Polygon 23:05
Taken (TRM): Ethereum about USD 3.79B (200,630 ETH, 1.875B USDT, 823M USDC, 88.5M RLUSD, 185 other tokens); 18,270 BTC (about 1.47B); 612.7M USDT and 46.4M TRX (about 628M); 233.46M XRP (about 296M); 970,500 SOL (about 96M); Arbitrum, Optimism, Base about 39M; Avalanche about 28M; Polygon about 10M
Technique (TRM, Elliptic): validly signed transfers on most chains; on Ethereum, 50 pre-signed EIP-7702 authorisations delegating a hot wallet to a sweeper contract
Intrusion (Binance, 3 November): tampered Homebrew install (June); fake job interview and malicious assignment repository (September); pyenv component replaced at /opt/homebrew/Cellar/pyenv/2.8.0/libexec/pyenv (3,414 bytes, was 3,344); internal AI tool used to reach two more engineers (20 October); container deployed with a stolen token, 17:15 to 19:56 (29 October)
Containment: last transfer 23:56 UTC (2,961.9 ETH); delegation cleared 00:10 UTC 30 October by authorising Binance14 to the zero address
Attribution: TraderTraitor (FBI, 31 October; TRM and Chainalysis earlier)
Blocklists: FBI published 628 addresses (608 ETH, 19 BTC, 1 SOL); Elliptic offers a free blocklist of the attributed addresses

//Sourcing and Uncertainty

The timeline, per-chain amounts, the EIP-7702 mechanics, the 50-nonce detail and TRM's reading of it, the staging and rehearsal, the issuer-by-issuer freezes, the laundering trades and the remaining USD 2.4 billion are from TRM Labs' post, with figures as of 00:30 UTC on 30 October. The USD 6.43 billion figure, the eleven-chain count, the 2.85 billion verified frozen, the 94% stablecoin share, the 3.25 billion still held and the Tron laundering pattern are from Elliptic. Binance's laptop and container statement, Teng's quotes, the response actions and the FBI's address counts and laundering note are from BleepingComputer's reports; the FBI alert itself returned an error when we fetched it. Teng's "multi-signature protocol" description is as reported by the BBC and summarised on Wikipedia; we have not seen the original. The description of EIP-7702 is from the Ethereum standard. The 23:35 Binance frozen figure is as reported by TRM.

The update section is from Binance's 3 November report, read on 12 November; the quotes are from it.

What is unknown. The AI coding tool, the search engine, the job platform and the internal AI tool are not named. Binance does not say how the internal tool gave the attacker control of other machines, how the June exposure led to the September approach, or what time zone its 17:15 to 19:56 window uses. Its findings are preliminary and an independent review is under way.