Within a single night, billions of dollars in digital assets left wallets associated with Binance. Stopping the attacker was only the beginning. The market now needs to know how transaction-authorisation controls were compromised, how much of the frozen money will actually return, and when customer balances will again be fully backed by assets.
On 30 October 2026, Binance estimated the security incident's impact at 6.3 billion USD and said roughly 3 billion USD had been frozen on-chain. It pledged to absorb losses using the SAFU fund and company resources and said users' funds were safe. But the intrusion path remained under investigation, and the company's assurance was not an independent audit of restored reserves.
On-chain analysts trace the incident to 29 October UTC, early 30 October in Thailand. They identified transfers from Binance-linked wallets into addresses attributed to the attacker. Their estimates differ on losses, networks and freezes because their wallet clustering methods and observation times are not identical.
What happened from the preparations to the shutdown
Bitquery found that the attacker prepared fee-paying wallets before the major withdrawals. TRM Labs identified advance Ethereum authorisations, suggesting premeditation. Neither blockchain record establishes who operated the internal computers or how an employee laptop was first breached.
| UTC time | Thailand time | Verified or reported event |
|---|---|---|
| 2026-10-29 14:54 | 2026-10-29 21:54 | Bitquery traces ETH funding to attacker fee wallets |
| 2026-10-29 20:04 | 2026-10-30 03:04 | First suspicious XRP Ledger transactions in Bitquery data |
| 2026-10-29 20:20-20:24 | 2026-10-30 03:20-03:24 | Bitcoin/TRON activity and Ethereum transfers of 167,464 ETH plus ~1.6bn USDT |
| 2026-10-29 21:01-21:05 | 2026-10-30 04:01-04:05 | Tether and Circle start asset freezes |
| 2026-10-29 22:33 | 2026-10-30 05:33 | Binance temporarily suspends withdrawals, according to Bitquery |
| 2026-10-29 23:56 | 2026-10-30 06:56 | Last Ethereum wave included in Bitquery chronology |
| 2026-10-30 00:10-00:18 | 2026-10-30 07:10-07:18 | Ethereum authorisations revoked; Arbitrum-related assets locked |
| 2026-10-30 02:23 | 2026-10-30 09:23 | Binance publishes preliminary impact of ~6.3bn USD |
The times and wallet associations come from Bitquery's on-chain investigation and Binance announcements, not a Binance-certified minute-by-minute reconstruction. Small timestamp differences may reflect differing recording methods.
A staff laptop may have opened the door, but withdrawal authority was the weakness
According to Binance's preliminary statement, an engineer's DevOps laptop may have been compromised, allowing access to a service container and submission of unauthorised withdrawals. Binance said it had found no evidence of a private-key leak at that stage.
These statements are compatible. An attacker may abuse a service authorised to request signatures or initiate withdrawals without ever personally possessing the private key. Investigators must determine the container's permissions, authorisation chain, transaction limits, recipient checks and why large abnormal transfers were allowed to continue.
The public record does not establish whether the original access involved phishing, malware, a zero-day vulnerability or collusion. Presenting any one of these possibilities as a proven cause would go beyond the evidence.
Why Ethereum became central to the attack
A closely watched transaction moved 167,464 ETH, around 1.6 billion USDT and other tokens from the wallet labelled Binance 14 to another address in one operation. TRM Labs and the Aave risk community also examined about 28,006 ETH sent from another Binance wallet.
The technical focus is EIP-7702, a mechanism that lets an Ethereum externally owned account authorise certain delegated smart-contract operations via signatures. TRM Labs assessed that the attacker used pre-arranged authorisations to make a major wallet execute asset-sweeping code, identifying 50 pre-signed authorisations.
This does not mean Ethereum itself was hacked, nor prove a flaw in EIP-7702. The question is how a hostile actor obtained, induced or exploited the necessary authorisations, and whether a custodian's separation of powers could have stopped their execution.
How much of the 6.3 billion dollars was stolen and how much was frozen?
Three quantities must remain separate: assets transferred away, tokens frozen or locked against further movement, and money actually recovered or replenished. They are not interchangeable.
| Affected value | Reported figure | Meaning and limitations |
|---|---|---|
| Estimated impact per Binance | ~6.3 billion USD | Company estimate; final asset list pending |
| On-chain transfers per TRM Labs | ~6.36 billion USD | Transfer-time valuation over ten networks |
| Frozen per Binance | ~3.0 billion USD | Frozen on-chain, not returned to Binance |
| Locked per TRM Labs | ~2.7 billion USD | Stablecoins and Arbitrum at TRM snapshot |
| Bitcoin traced by analysts | ~18,270 BTC | No issuer with unilateral freeze powers comparable to some stablecoins |
Why nine networks in one report and ten in another? Bitquery mapped 17 main wallets across nine networks; TRM Labs counted ten networks of connected activity. That is a methodological difference requiring a transaction-by-transaction comparison, not evidence that one report is necessarily false.
Frozen is not recovered. Stablecoin issuers such as Tether and Circle can restrict eligible tokens, but returning them still entails legal, technical and ownership steps. BTC, or ETH controlled by an attacker on Ethereum mainnet, cannot simply be frozen by an issuer in the same way.
TRM Labs reported about 2.67 billion USD frozen by stablecoin issuers, plus roughly 30 million USD affected by action involving the Arbitrum Security Council. Binance's approximately 3 billion USD figure represents a different reporting snapshot and must not be added to TRM's figure.

Who is suspected, and where does the investigation stand?
TRM Labs attributed the incident to TraderTraitor, associated with North Korea, with high confidence based on its on-chain and off-chain intelligence. The FBI had previously attributed a separate roughly 1.5 billion USD Bybit theft in February 2025 to the same group.
Similar methods do not amount to judicial proof of identity. As of 30 October 2026 no public disclosure verified an arrested or charged suspect in this Binance incident. Binance said it was working with law enforcement and blockchain investigators.
Money-laundering routes matter as much as the initial access. Tokens can be swapped, moved through exchange venues and used in DeFi protocols. Aave risk analysts described a deposit of 60 million USDT and a borrowing transaction involving 19,762 WETH associated with addresses they traced to the attacker. TRM Labs noted attempts to turn freezeable tokens into assets less subject to unilateral issuer controls. Wallet clustering alone does not reveal the real-world beneficial owner.
What Binance has contained and what remains unknown
Binance reported temporarily suspending deposits and withdrawals, revoking affected authorisations, coordinating with token issuers and law enforcement on freezes, and tracing asset flows. It said a comprehensive technical post-mortem would follow after verification.
Emergency containment does not demonstrate that every systemic weakness has been repaired. Four questions remain: what privileges the container had, whether signing authority was genuinely separated across wallets, why anomaly controls did not stop enormous withdrawals sooner, and whether an independent security review occurred before full operations resumed.
Customer reserves are another unresolved test. CoinDesk compared the attacked wallets with Binance's 1 October Proof of Reserves snapshot and estimated that ETH coverage could temporarily fall without replenishment. That is a scenario based on an older snapshot, not a contemporaneous audit proving insolvency or disproving Binance's promise to replace assets. The meaningful evidence will be actual replenishment, updated asset-by-asset reserve ratios, and a verifiable root-cause report.
How Thai users and the crypto market are affected
Gulf Binance, which operates Binance TH, said on 30 October that it is a separate legal entity with separate custody and cold-wallet arrangements. It stated that customer assets at Binance TH were safe, while temporarily stopping crypto deposits and withdrawals for checks and leaving other services available. These remain the operator's assurances, not independent audits.
Associated Press reported Bitcoin down 3.2% to below 79,000 USD on the US evening of 29 October. The security news weighed on sentiment, but a price move cannot be attributed entirely to one event when liquidity, broader risk appetite and macroeconomic data also matter. Users face both custody risk and the practical cost of temporarily losing access to funds. They should follow official service notices and beware of fake compensation or account-verification links.
Losses by asset and amounts verifiably frozen
Ranked by the approximate value of assets originally transferred out of Binance on 29-30 October, USDT came first, followed by BTC, USDC and ETH. Values reflect the transfer period, not subsequent attacker holdings after swaps, and are not net losses after reimbursement.
| Asset | Value moved out of Binance | Confirmed frozen or locked |
|---|---|---|
| USDT | ~2,500,000,000 USD (across several networks) | ~1,770,000,000 USD |
| BTC | 18,270 BTC (~1,470,000,000 USD) | No confirmed frozen amount |
| USDC | 823,000,000 USDC (~823,000,000 USD) | ~823,000,000 USDC |
| ETH | 200,630 ETH (Ethereum) + 8,426 ETH (Arbitrum), >480,000,000 USD | 8,426 ETH (Arbitrum, ~19,500,000 USD) |
| XRP | 233,460,000 XRP (~296,000,000 USD) | No confirmed frozen amount |
| SOL | 970,500 SOL (~96,000,000 USD) | No confirmed frozen amount |
| RLUSD | ~88,500,000 USD | ~40,500,000 USD |
| WBETH | 29,934 WBETH (~76,900,000 USD) | 29,934 WBETH (~76,900,000 USD) |
| XAUt | 12,574 XAUt (~50,600,000 USD) | 12,574 XAUt (~50,600,000 USD) |
| UNI | ~49,600,000 USD | No confirmed frozen amount |
| ENA | ~44,700,000 USD | No confirmed frozen amount |
| PEPE | ~40,100,000 USD | No confirmed frozen amount |
| LINK | ~29,600,000 USD | No confirmed frozen amount |
| USD1 | ~27,800,000 USD | ~27,800,000 USD |
| TRX | 46,400,000 TRX (~16,000,000 USD) | No confirmed frozen amount |
| ARB | 74,600,000 ARB (~12,300,000 USD) | 74,600,000 ARB (~12,300,000 USD) |
| PAXG | 1,907 PAXG (~7,700,000 USD) | 1,907 PAXG (~7,700,000 USD) |
The ETH and TRX later held by the attacker were partly bought with other stolen tokens and must not be counted as a second theft. Similarly, USDC frozen after swaps should not be counted again as USDC originally removed. Figures for USDT span multiple networks and are approximate.
A blank confirmed-freeze figure does not mean authorities will never recover anything. The ETH lock pertains specifically to Arbitrum, not an issuer-style freeze of ETH on Ethereum mainnet. Other smaller tokens cannot yet be ranked safely from published information.
Across all assets, Binance's estimate remains 6.3 billion USD affected and around 3.0 billion USD frozen. TRM Labs estimated roughly 6.36 billion USD transferred and 2.7 billion USD locked using its own snapshot. The differing timestamps and accounting scopes preclude adding the freeze figures together. A freeze is not a returned asset. Sources: TRM Labs, Bitquery and OnChain Benchmark, reviewed 30 October 2026.
The answers the market still needs
The Binance incident is a stress test of institutional custody controls rather than simply a story of stolen coins. The preliminary evidence shows how withdrawal authority may be abused even if there is no established leakage of private keys.
Key takeaway Freezing around 3 billion USD is progress in containing damage, not proof of recovery or comprehensive security remediation. Confidence will depend on a checkable technical post-mortem, returned or replenished reserves, and evidence that abnormal withdrawals can no longer pass authorisation controls so easily.



