The short version
- The theft. On 29 October an attacker moved roughly $6.36 billion out of Binance wallets across ten blockchains, most of it within about 20 minutes from 20:05 UTC, according to TRM Labs. Binance puts the loss at about $6.3 billion and says it will cover it from its Secure Asset Fund for Users and company funds.
- How it started. Binance's first account points to a compromised DevOps engineer's laptop that gave an attacker access to a service container and the ability to submit unauthorised withdrawal transactions. A later statement describes fake recruiters, a malicious coding assignment and stolen credentials used to reach further engineers.
- What was frozen. Tether, Circle, Ripple, World Liberty Financial and Arbitrum's Security Council froze roughly $2.7 billion in stablecoins and tokens, a figure Binance puts at about $3 billion. TRM says the attackers still hold more than 420,000 ETH and 18,270 BTC, about $2.4 billion that no issuer can freeze.
- Attribution. TRM Labs and Chainalysis attributed the theft with high confidence to TraderTraitor, a North Korean unit also tracked as Lazarus Group and APT38; Elliptic also attributed it to North Korean hackers. The FBI named the group in an alert on 31 October and published 628 addresses linked to the laundering; North Korea's Kim Yo Jong dismissed the claim as a provocation.
Timeline
| Date | Event |
|---|---|
| 29 Oct | From about 20:05 UTC, roughly $6.36 billion leaves Binance wallets across ten blockchains, most of it within 20 minutes; Binance confirms a breach and suspends deposits and withdrawals. |
| 30 Oct | By 00:30 UTC TRM tallies about $2.7 billion frozen by stablecoin issuers and Arbitrum; Binance says it has frozen just under half of the stolen assets. |
| 31 Oct | The FBI publishes an alert attributing the theft to TraderTraitor and lists 628 cryptocurrency addresses used to launder funds. |
| 1 Nov | Binance says it is preparing to resume the first phase of withdrawals between 06:00 and 09:00 UTC and that it has covered about 95% of the affected amount. |
| 3 Nov | Binance publishes a detailed account describing fake recruiters, a malicious coding assignment and stolen credentials; it says the attack should not have happened. |
| 4 Nov | North Korea fires several missiles toward the sea; Kim Yo Jong again rejects the FBI attribution. |
How the money left
Transfers began at about 20:05 UTC on 29 October and most of the funds were gone within 20 minutes, according to TRM Labs, which tracked about $6.36 billion leaving Binance wallets across ten blockchains. Binance has put the loss at roughly $6.3 billion. The Record reported that assets moved across 20 blockchains; TRM and SecurityWeek say ten.
The first reports on 29 October were unsettled. Arkham Intelligence was tracking 55 addresses worth about $5.78 billion, but that was the value of holdings across those wallets rather than a confirmed loss, and Binance had confirmed only that it was investigating. Binance said customer funds were safe and warned users about scams.
TRM's on-chain reconstruction describes preparation over at least a day and a half, an operator wallet funded through small Tornado Cash withdrawals, and malicious code tested on other wallets first. On Ethereum the attackers used EIP-7702, a mechanism letting a wallet delegate its behaviour to a smart contract, sending 50 pre-signed permissions so one would match the wallet's transaction count. TRM concluded the attackers most likely gained the ability to make Binance's hot wallet signing system sign transactions of their choosing across chains.
How the attackers got in
Binance's initial investigation said the incident may involve a compromised DevOps engineer's laptop, which let an attacker reach a service container and submit unauthorised withdrawal transactions. The company said it found no evidence of a wallet private key leak and would publish a technical post-mortem once facts were verified.
In a statement on 3 November, Binance described the route in more detail: people posing as recruiters contacted a wallet engineer, held two interviews and sent a coding assignment that carried malicious code onto the engineer's work laptop, which Binance's security tools did not detect. From there the attackers used an internal tool to reach the work computers of two other wallet engineers. One of those had downloaded a tampered app containing password-stealing malware months earlier after finding it through a search engine; his laptop was replaced, but stolen credentials were used to reach a third engineer with access to systems controlling funds.
Binance said the attack should not have happened, that it had improved network security and would bring in outside experts, and that it had faced at least 57 suspected North Korean attacks. It also said it had uncovered additional points of breach without describing them. A spokesperson declined to answer questions on how Binance prevents untrusted code running on employee laptops or whether third parties had audited its network.
Freezes, attribution and the denial
Stablecoin issuers moved quickly. By 00:30 UTC on 30 October TRM counted about $2.7 billion frozen, including roughly $1.77 billion in USDT locked by Tether and about $825 million in USDC by Circle; Ripple and World Liberty Financial froze smaller sums and Arbitrum's Security Council moved about $30 million out of an attacker wallet. Binance estimates the frozen total at about $3 billion. TRM says the attackers sold USDT below market and borrowed ETH against USDT on Aave to stay ahead of the freezes.
TRM attributed the attack to TraderTraitor with high confidence, citing on-chain and off-chain intelligence and similarities to the Bybit and KelpDAO thefts. Chainalysis said it held the same view with a high degree of confidence, noting proceeds from the Bitget exploit mixed with Binance funds; Elliptic also blamed North Korean hackers, and researcher ZachXBT named Lazarus. Binance itself has not publicly identified the hackers and says it is working with law enforcement.
The FBI's 31 October alert said North Korea was responsible for the theft of more than $6 billion in virtual assets from Binance on or about 29 October. It said TraderTraitor was converting assets mainly to Ethereum and expected further laundering through decentralised finance platforms and instant swap services, and it asked exchanges and other virtual asset service providers to block transactions tied to 628 listed addresses, most of them Ethereum. North Korea rejected the finding: Kim Yo Jong called it a trite provocation and part of Washington's hostile policy, and missiles were fired on 4 November.
What is not known yet
- Whether the final stolen figure will change; early reporting ranged from about $3.48 billion to $6.36 billion before Binance settled on roughly $6.3 billion.
- Which systems beyond the engineer laptops were breached; Binance said it found additional points of breach but has not described them.
- Whether any customer data, account records or personal information was accessed in the intrusion.
- Whether Binance will publish the updated proof of reserves it promised once remediation is complete.
- Whether the roughly $2.4 billion in ETH and BTC still held by the attackers can be traced and recovered.
What to do
If you hold funds on Binance
- Check Binance's official channels for the current status of deposits and withdrawals before attempting a transaction.
- Treat unsolicited messages, links or requests for account information about the incident as fraudulent; Binance has warned of scams and says it will communicate through official channels only.
If you run an exchange or virtual asset service provider
- Screen transactions against the 628 addresses in the FBI alert, which lists 608 Ethereum, 19 Bitcoin and one Solana address.
- Watch for stolen assets arriving as Ethereum through decentralised finance platforms and instant swap services, which the FBI expects to be the main laundering routes.
- Report addresses and transfers linked to the theft to the law enforcement contacts given in the alert.
For everyone else
- Treat recruitment approaches and take-home coding exercises from unknown parties as untrusted code; do not open or run them on a work device.
- Download software only from vendor-controlled sources rather than search results, which is how one of the compromised Binance laptops was infected with password-stealing malware.
- Revoke credentials and sessions for any account used on a machine that ran untrusted software, since replacing the laptop alone did not stop the attackers reusing stolen logins.
Update log
- First published.
Sources
- North Korea Launches Missiles Toward the Sea as Pyongyang Protests Against US Claims on Binance Hack
- Researchers warned of North Korean hacking tactics years before record $6.3B Binance heist
- FBI links $6.3 billion Binance crypto heist to North Korean hackers
- North Korean hackers blamed for stealing record $6.3B in Binance breach
- Binance links $6.3 billion crypto theft to compromised DevOps laptop
- $6 Billion Binance Hack Bears Hallmarks of North Korea’s TraderTraitor
- Binance hit by record $6.3 billion crypto hack, scrambles to freeze funds
- Binance probes potential $5.8 billion crypto-theft hack
New incident reports by email
One email a week with the reports published since the last one.