Binance Post-Mortem Dates $6.3 Billion Breach to June and Fake Interview
Security / news
Binance Post-Mortem Dates $6.3 Billion Breach to June and Fake Interview
The exchange says two engineers were targeted four months apart, and that an internal AI tool let the attacker move between wallet developers on Oct. 20.

Binance says an attacker held two wallet developers' systems for nine days, from Oct. 20 to Oct. 29, before draining $6.3 billion in crypto, and that the intrusion began in June. The exchange published its account on Tuesday, Nov. 3, five days after the theft.
Binance said two separate employees were targeted through two different lures. NBC News, relaying Reuters reporting, and Fortune both reported the details; the two outlets differ on one of them.
The June download and the September interview
In June, an employee on Binance's wallet developer team clicked an advertisement for a tampered tool. NBC and Reuters describe it as a tampered AI tool. Fortune, quoting Binance's account, describes a tampered version of Homebrew, the macOS package manager. Binance said it detected the download, replaced the device and changed credentials, but the attacker had already learned who managed the company's wallets.
In September, a second engineer, identified only as Software Engineer B, was contacted through a job-hunting platform by someone posing as a Project Director. Fortune's headline names LinkedIn; Binance's quoted wording says only "a legitimate job-hunting platform." The fake recruiter arranged a first-round interview with an HR representative and a second round with a person claiming to be chief executive of a fictitious company. The interviews ended with an "assignment", which NBC describes as a malicious code repository.
| Date | What Binance says happened |
|---|---|
| June | Wallet-team employee downloads tampered tool; device replaced, credentials rotated |
| September | Software Engineer B interviews for a fake role and runs the "assignment" |
| Oct. 20 | Attacker uses that laptop and an internal AI tool to take over two wallet developers' systems |
| Oct. 29 | Script launched from the second developer's machine using the first developer's stolen credentials |
How the internal AI tool was used
On Oct. 20, according to NBC, the attacker used the compromised computer and the internal AI tool to take control of two wallet developers' systems. Fortune quotes Binance saying the tool was used "to gain control over the Wallet DevOps Engineer A," whose machine held a container deployment permission token.
Binance told Fortune the attack relied mainly on conventional phishing and that AI played a part only in the later stage. The theft itself ran on Thursday, Oct. 29. TRM Labs, a blockchain forensics firm, put the outflow at about $6.36 billion across 10 blockchains. TechCrunch, citing TRM, reported the theft took about 20 minutes.
None of the accounts reviewed describe customer personal data being taken. The loss is wallet assets.

Who is blamed, and where the sources disagree
NBC, relaying Reuters, said the FBI has blamed a North Korean hacking group and that Pyongyang rejects the claim. TRM's Nov. 3 update says the opposite on one point: Binance has not published a root cause "and no government has attributed the theft." TRM itself attributes the theft to TraderTraitor, a North Korean state-sponsored unit, with high confidence, citing onchain and offchain intelligence.
The FBI claim reaches us through Reuters with no primary document attached.
What was frozen, and what is still moving
- Left Binance wallets6.36 billion USD
- Frozen within hours2.7 billion USD
- Still held by attacker (ETH and BTC)2.4 billion USD
Source: TRM Labs, Binance Hack Update, accessed 2026-11-04
Tether, Circle, Ripple, World Liberty Financial and the Arbitrum Security Council froze nearly $2.7 billion within hours, TRM said. Binance gives a different measure: Fortune reports about $2.5 billion recovered and 98 percent of the stolen coins replenished from reserves and other sources, with the remaining 2 percent in lesser-used currencies still being bought.
Binance re-enabled withdrawals on Saturday after about 48 hours. A spokesperson declined to say whether Software Engineer B broke Binance's rule that non-public-facing staff may not keep LinkedIn profiles, or whether anyone would be fired, Fortune reported.
On Oct. 30 The Terminal reported Binance's first account, which named only a compromised DevOps laptop. The new timeline moves the start of the intrusion back four months. It also echoes a pattern covered in a tampered Claude Code extension that sat in Cursor's marketplace: the entry point is a developer running code from a source the company did not vet.
Engineers who take outside coding assignments from recruiters should run them in a disposable virtual machine with no credentials. Binance has not yet said when its updated proof of reserves will be published.
Sources
More in Security
- 01Ruby2Shell (CVE-2026-132825): Ruby Is Fixed, but GitLab, GitHub Enterprise and Chatwoot Are Listed Without a PatchA one-byte heap overflow in Ruby's case conversion carries a 7.4 local score, while the researchers say stock Rails is remotely reachable and will publish a proof of concept Nov. 25.
- 02NPCI Wants Overlay Permissions Restricted on Sideloaded Apps; Google's 2024 India Block List Omits ThemThe reported ask covers accessibility, device admin and display-over-apps. The pilot Google announced on Oct. 3, 2024 named four other permissions.
- 03CVE-2026-99312: A KVM Nested-AMD Bug Scores 8.8, With Fixes Listed for Three Kernel BranchesThe Linux CNA's scoring notes describe a freed page-table root that a guest can aim at; the commit message describes only a stale MMU context.
- 04CISA's Nov. 18 KEV Additions Include Apache Axis 1.x, Which Has No Fix, With a Nov. 21 DeadlineThree of four new entries carry a three-day federal deadline; LiteLLM's advisory names two different patched versions.