What We Know About the Binance Hack, the Largest Crypto Theft on Record
A UTC timeline of the 20 minutes that emptied Binance's hot wallets, how analysts say the signing system was turned against it, what Tether and Circle froze, and who is naming North Korea.
Friday, October 30, 2026/5 min read

By the time most of Europe sat down to dinner on Thursday, the largest theft in the history of cryptocurrency was already over. Between about 20:05 and 20:25 UTC on 29 October, Binance wallets on at least ten blockchains emptied into addresses nobody at the exchange controlled. Binance now puts the damage at about $6.3 billion, roughly four times the Bybit theft of February 2025, and says the figure may still rise.
We reported the first outflows and freezes on Thursday night and Binance's $6.3 billion estimate and the compromised laptop early on Friday. This is the fuller account as of mid afternoon on 30 October.
Binance hack timeline in UTC
The preparation started a day earlier. According to TRM Labs analysis summarised by CryptoSlate, an attacker wallet was funded through the Tornado Cash mixer on the morning of 28 October, then rehearsed malicious contract code on fresh Ethereum wallets, the last run about four hours before the real thing.
- 29 October, 20:05 to 20:09: five Binance wallets on the XRP Ledger send about 233 million XRP, worth roughly $296 million, to one attacker address. Suspicious transfers then begin on Solana and Optimism.
- 20:20: a Binance bitcoin wallet sends 18,270 BTC, about $1.47 billion. In the same minute, 50 pre-signed EIP-7702 authorisations are submitted against the Ethereum hot wallet labelled Binance 14.
- 20:23: the sweep fires: 167,464 ETH and 63 tokens, including about 1.6 billion USDT, leave in one transaction. Within two minutes a Tron wallet sends 612.7 million USDT and 46.4 million TRX.
- About 21:15: Binance says it is investigating a potential security issue and warns of scams. Around 21:52 Changpeng Zhao posts that funds are safe and thanks Tether and Circle, whose chief executives say they have frozen more than $1.57 billion of USDT and more than $800 million of USDC.
- 22:30 to 23:00: withdrawals are paused; Aave freezes its lending markets after the attacker borrows ether against stolen USDT. A second wave hits Avalanche and Polygon around 23:05 and sweeps continue until 23:56.
- 30 October, 00:07: deposits are suspended and Binance says it will cover all losses. By 00:52 it puts frozen assets at $3 billion.
- 02:25: Binance gives the $6.3 billion estimate and says a compromised DevOps engineer's laptop may be involved.
- 04:17: withdrawals to resume within 48 hours. 08:37: Binance says it has found "additional points of breach". 10:55: it reserves more than $6.34 billion of company funds.
- 14:34: co-chief executive Richard Teng targets withdrawals within about 40 hours and a full proof of reserves by Monday.
The timestamps follow the Cointelegraph live log, which runs in UTC, checked against CoinDesk's and Euronews's logs.
How the Binance hack happened, as far as anyone has said
Binance's own account has moved. Its 02:25 statement said a compromised DevOps engineer's laptop may have let an attacker reach a service container and submit unauthorised withdrawals, with no evidence of a private key leak. Six hours later it reported other points of breach, and Teng wrote that the attacker did not simply use one engineer's permissions and that this was not a single one-click action. A technical post-mortem is promised, not published.
Analysts fill in some mechanics. On Ethereum the attacker used EIP-7702, a feature from the May 2025 Pectra upgrade that lets an ordinary wallet temporarily run contract code. TRM Labs and Chainalysis say 50 authorisations signed by Binance 14 turned the wallet into a sweeper the attacker controlled, as Decrypt reports. TRM's larger point is that on the other nine chains the funds left through ordinary signed transfers, which it reads as a compromise of Binance's hot-wallet signing infrastructure rather than a flaw in Ethereum. Teng said on Friday afternoon that the delegation did not pass through Binance's normal approval controls and that the attacker used a self-destruct mechanism to erase traces.
Where the $6.3 billion figure comes from
The number is Binance's own estimate, published at 02:25 UTC, and it sits inside a cluster of independent tallies that value each asset at the moment it moved: TRM Labs about $6.36 billion across ten chains, Chainalysis at least $5.912 billion as of 00:30 UTC and later about $6.4 billion, Elliptic $6.43 billion across 11 chains, including $3.80 billion on Ethereum and $1.48 billion in bitcoin.
What is frozen is clearer: Tether more than $1.567 billion, Circle more than $800 million, Ripple about $200 million of RLUSD, World Liberty Financial about $27 million, and the Arbitrum Security Council about $30 million of ETH and ARB. Binance's round figure is $3 billion; Elliptic has verified $2.84 billion, 44 percent of the theft, almost all stablecoins. Roughly $3.2 billion to $3.3 billion in ether, bitcoin and other assets no issuer can freeze remains with the attacker.
Who pays, and when withdrawals come back
The SAFU emergency fund, created in 2018 and holding about $1 billion in bitcoin, was never going to cover this alone. On Friday Binance said it had reserved more than $6.34 billion of company funds, excluding the frozen assets, with about $5 billion already held in the exact tokens stolen and the rest being bought on the market and over the counter. CertiK and Nansen told Cointelegraph they could not yet verify the $5 billion on-chain. Teng says a full proof of reserves will follow by Monday 2 November and that customer assets were not touched.
Who is blaming North Korea
No government has named a culprit, and Binance says its investigation has not attributed responsibility to anyone. The attribution so far comes from private analysts. TRM Labs says, with what it calls high confidence, that the attack was the work of TraderTraitor, a North Korean unit it links to the Lazarus Group, citing staging and signature patterns that match the Bybit theft and April's KelpDAO exploit. Chainalysis chief executive Jonathan Levin said his firm reached the same conclusion because the stolen funds were commingling in real time with proceeds of September's Bitget hack. Elliptic calls DPRK involvement likely but notes the attacker was unusually slow to convert stablecoins, which is what allowed the freezes. ZachXBT called Lazarus the likely attacker, and Blockaid's Ido Ben-Natan said the tactics matched North Korean operations, CoinDesk reported. North Korea has denied previous hacking allegations, and the FBI, which named TraderTraitor for Bybit within five days, has said nothing about this case so far.
How it compares with Bybit and the old records
Bybit lost about $1.46 billion in February 2025 after a developer's machine at Safe{Wallet} was compromised, the previous record; before that came Ronin at about $625 million in 2022 and Poly Network at about $610 million in 2021. TRM counts about $2.9 billion stolen in all of 2025; Binance lost more than twice that in 20 minutes. Elliptic notes both exchanges fell to compromised infrastructure and people rather than broken cryptography, and that the Bybit funds took months to launder.
Next comes a weekend of waiting: withdrawals back on, the promised reserves report, and an explanation of how a laptop and whatever else was breached ended up signing away $6 billion. The attacker holds more than $3 billion that nobody can freeze, and the people paid to watch those wallets expect them to move.
Published in The Outspoken Digest
Newsletter
The Digest, in your inbox
One edition, sent when it is ready. No noise, and your address is never passed on.
Read Next
More Crypto →
Only Abu Dhabi's Regulator Has Spoken on the Binance Hack, While Washington Stays Silent and Rivals Offer Help
Oct 30, 2026/4 min read

Bitcoin Holds Near $77,000 After the Binance Hack as $1.57 Billion in Leverage Is Wiped Out
Oct 30, 2026/4 min read

Binance Puts the Damage at $6.3 Billion, Blames a Compromised Engineer's Laptop and Promises to Cover Every Loss
Oct 30, 2026/2 min read
