🔍 Read the full analysis: Binance’s Hack, Minute By Minute: What’s Clear And What Isn’t on ThorstenMeyerAI.com
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
On Oct. 29, an attacker drained Binance hot-wallet funds in a series of transactions across several blockchains. Binance estimates the impact at about $6.3 billion, says it will cover losses and reports that roughly $3 billion was frozen; the estimate is preliminary, and the cause has not been fully established.
Binance said a security incident affected about $6.3 billion after an attacker drained its Ethereum hot wallet and funds moved from other Binance wallets across multiple blockchains on Oct. 29. The exchange said it would cover losses and user funds were safe, while deposits and withdrawals were suspended as it investigated. The impact and freeze totals remain estimates, and Binance has not yet published a full post-mortem.
The first major confirmed movement in the public Ethereum record occurred at 20:24 UTC on Oct. 29. A transaction sent 167,464 ETH, 1.615 billion USDT and 62 other tokens from a Binance hot wallet labelled Binance 14 to a newly created wallet. Blockworks valued that transaction at roughly $2.5 billion. Another Binance wallet sent 28,005.6 ETH to the same address 24 seconds later, according to the account of the public chain record in the source report.
Outflows had begun on several networks at about 20:05 UTC, according to blockchain security firm TRM Labs. It said Binance wallets on Bitcoin, Tron, the XRP Ledger, Solana and other networks sent funds through ordinary signed transfers. A further wave reportedly affected Avalanche and Polygon later in the evening. Binance’s early Oct. 30 incident update put the estimated total impact at about $6.3 billion and said roughly $3 billion had been frozen. Those figures are preliminary and depend on the assets counted, valuation time and subsequent tracing.
Binance said a compromised DevOps engineer’s laptop may have enabled access to a service container used to submit unauthorized withdrawals. The exchange said it had found no evidence that a wallet private key was leaked. It also said it revoked the affected address authorization. The source report says Binance 14 no longer ran the attacker’s code by the morning of Oct. 30. Binance has not yet issued the promised detailed post-mortem, so the precise access path and full accounting are not established.
Infographic 01 · The evening of 29 October 2026
How billions left Binance in one evening.
From the staging to Binance’s statements, in UTC (ET = UTC − 4 on 29 Oct). “On-chain” items were checked in the public Ethereum record.
- 28 OctOperator wallet fundedTRMThree small withdrawals from the Tornado Cash mixer
- 13:51–16:47Tests and a rehearsalon-chainSweeper code tried on three small wallets; the final contract deployed at 15:59
- ≈ 20:05Outflows begin on several chainsTRMMost within about 20 minutes
- 20:20:59Binance 14 taken overon-chainOne transaction, 50 EIP-7702 permissions, one valid
- 20:24:23The sweepon-chain167,464 ETH, 1.615 billion USDT and 62 other tokens leave in one call. 24 s later: 28,005.6 ETH from Binance 16
- 20:38:47195,460 ETH forwardedon-chainTo a brand-new wallet that had sent nothing when checked on 30 Oct
- 20:41 / 20:59Hot Wallet 34 drainedon-chain780 million, then 43 million USDC from a smart account Binance 14 controlled
- 21:18–22:56The freeze raceBlockworksCircle, Tether, Ripple, World Liberty Financial with BitGo, Paxos
- 21:29Binance’s first statementX“Actively investigating. User funds are completely safe.”
- 22:15Withdrawals haltedXBinance: they resume “as soon as the security issue is fully resolved”
- ≈ 23:05Second waveTRM · on-chainAvalanche and Polygon; sweep calls on Binance 14 continue to 23:56
- 30 Oct 02:23“Security Incident Update”Binance~$6.3B impact, ~$3B frozen, compromised DevOps laptop, no evidence of a key leak
- 04:17Service updateYi HeDeposits “operate as normal”; withdrawals to begin resuming within 48 hours
Sources: Ethereum record, checked by Thorsten Meyer AI on 30 Oct; TRM Labs (as of 00:30 UTC); Blockworks reporting (29 Oct, converted from ET); Binance, 30 Oct 2026; Binance posts on X, 29 Oct; Yi He, 30 Oct. All figures preliminary.
Powered by Thorsten Meyer AI
Why the Multi-Chain Loss Estimate Matters
The incident matters because the reported transfers involve billions of dollars across several networks, not just one Ethereum wallet. Binance’s estimate, if confirmed, would make the event one of the largest reported crypto thefts. The source compares the preliminary $6.3 billion figure with the $1.5 billion Bybit hack in February 2025; that comparison depends on Binance’s estimate holding up and should not be treated as a final ranking.
The response also highlights a distinction between assets that can be frozen by their issuers and assets that cannot. The source report says stablecoin issuers froze about $2.5 billion to $3 billion within hours, while TRM estimated about $2.4 billion in assets beyond issuer control. These are attributed, early counts rather than a verified final recovery total. For customers, the immediate practical issues were paused withdrawals, the status of deposits and Binance’s assurance that it would absorb losses.
Popular right now

Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Bluetooth 5.3, USB-C Charging, IPX4, Black

LG OLED evo C4 55-Inch 4K Smart OLED TV (OLED55C4PUA) with 144Hz Refresh Rate, HDMI Cable, 24-Month Protection Plan, and Streaming Bundle

Samsung 55-Inch S90H OLED 4K UHD Smart TV Bundle with Full-Motion Mount and Surge Protector
As an affiliate, we earn on qualifying purchases.
How Binance 14 Was Taken Over
The reported Ethereum mechanism involved EIP-7702, a feature that allows an externally controlled account to authorize code to act on its behalf. The source says the attacker submitted a transaction carrying 50 permissions tied to consecutive transaction numbers, or nonces, for Binance 14. According to blockchain security firm Blockaid, one permission matched the wallet’s current nonce, allowing the attacker’s code to run. The wallet was then used to sweep assets.
The timeline described in the source shows preparation before the main theft. On Oct. 29, the operator tested code on small wallets, deployed a contract and rehearsed it before the large outflows. At 20:20:59 UTC, the permission transaction was recorded; the major sweep followed at 20:24:23. These technical details are based on the cited analysts’ interpretation and the source author’s review of public Ethereum records. Binance’s own full technical explanation remains pending.
Binance first posted publicly at 21:29 UTC, saying its teams were investigating a potential security issue and that user funds were safe. At 22:15, it said withdrawals would resume once the issue was resolved. Its early Oct. 30 update reported the estimated impact, freezes and suspension of deposits and withdrawals. Co-CEO Yi He later said withdrawals were expected to begin resuming within 48 hours of her post, while deposits were operating normally.
The Unsettled Losses and Attribution
The final amount stolen or disrupted is not yet known. The source gives preliminary estimates ranging from at least $5.5 billion, attributed to Blockaid at 22:00 UTC, to about $6.36 billion from TRM Labs; Arkham’s estimate was $6.01 billion, and Binance put the impact at about $6.3 billion. These figures use different counting methods and valuation points. They should not be treated as a settled recovery-adjusted loss.
It is also unclear exactly how the attacker gained the ability to authorize the wallet code. Binance said a compromised employee laptop may have provided access to a service container, but did not establish that as the final cause. Its statement that it found no evidence of a private-key leak does not by itself explain how the permissions were created or how transfers on other networks were authorized. TRM’s attribution to TraderTraitor is an analyst assessment, not a confirmed finding by Binance or a government.
The eventual amount recovered, the distribution of losses among affected assets, and the timing of normal withdrawals also remained open in the source material dated Oct. 30. Stablecoin freezes do not establish that all frozen funds will be returned, and assets such as ETH and bitcoin cannot be frozen by a token issuer. Binance’s assurance that it will cover losses is important, but the source does not provide a detailed compensation process.
Withdrawal Resumption and Binance’s Review
Binance said it was working to restore withdrawals after suspending them during the investigation. Yi He’s Oct. 30 post gave a target of beginning to resume withdrawals within 48 hours; it did not confirm a completed restart. The exchange said deposits were operating normally. Customers should rely on Binance’s official channels for service notices and should be cautious of unsolicited messages claiming to offer refunds or account support.
The next major development is expected to be Binance’s detailed post-incident review, which could clarify how the attacker obtained authorization, what systems were affected, how the loss total was calculated and what protections will change. Updated information from blockchain analysts and stablecoin issuers may also refine estimates of frozen and traceable funds. Until those details are released, the cause, final financial impact and recovery outcome remain provisional.
Key Questions
How much did the Binance incident cost?
Binance estimated an impact of about $6.3 billion in its early Oct. 30 update. Other preliminary estimates cited in the source range from $5.5 billion to about $6.36 billion. The figures differ by method and valuation time, so there is no final confirmed total yet.
Were Binance customer funds safe?
Binance said user funds were safe and said it would cover losses. The source material does not include a full accounting of affected assets or a detailed compensation plan, so readers should distinguish the exchange’s assurance from a published post-mortem.
How did the attacker take the Ethereum wallet?
The source says the attacker used an EIP-7702 authorization to make Binance 14 run attacker-controlled code and then transfer assets. Blockaid’s analysis says one of 50 submitted permissions matched the wallet’s transaction number. Binance has not yet published a complete technical explanation.
Who was responsible for the attack?
TRM Labs attributed the incident with high confidence to TraderTraitor, which it links to North Korea. That remains an analyst attribution; the source says Binance and government officials had not confirmed it.
When will Binance withdrawals resume?
Co-CEO Yi He said on Oct. 30 that withdrawals were expected to begin resuming within 48 hours of her post. That was a forecast, not confirmation that withdrawals had restarted; Binance’s official service updates are needed for the current status.
Source: ThorstenMeyerAI.com
