[/blog]Web3 & Security4 min read

Binance $6.34 Billion Security Incident (October 2026): What Officially Happened

Official breakdown of the 29 October 2026 Binance hot-wallet incident: $6.34B impact, months-long campaign, EIP-7702 delegation, no private-key leak, SAFU coverage, and FBI attribution to North Korea. User funds were protected.

By Mussawar Hayat

What Happened on 29 October 2026

On 29 October 2026 at approximately 20:05 UTC, Binance’s hot wallets were compromised in a sophisticated security incident. Approximately USD 6.34 billion in digital assets were impacted. Binance has stated clearly that it will absorb the full financial impact through its Secure Asset Fund for Users (SAFU) and corporate treasury — user funds were not lost.

Key Official Facts

  • Incident began ~20:05 UTC on 29 October 2026
  • Total impact: ~USD 6.34 billion
  • No evidence of wallet private-key leak
  • Binance covering all losses (SAFU + treasury)
  • FBI attributes the attack to North Korea (TraderTraitor)
  • 98% of impacted assets replenished by 31 October (verifiable on Proof of Reserves)

How the Attack Unfolded (Official Timeline)

According to Binance’s initial findings report, this was not a single breach but a months-long campaign involving social engineering, malware, and internal tool compromise.

  • June 2026 — Supply-chain element: a Wallet DevOps engineer downloaded a tampered installer while setting up an AI coding tool.
  • September 2026 — Social engineering via a fake job interview on a recruitment platform. Malware (0-day, undetected by endpoint tools) was delivered and installed on an engineer’s machine.
  • 20 October 2026 — Attacker used a compromised computer and an internal AI tool as a pivot to expand access and obtain a container deployment permission token.
  • 29 October 2026 (17:15–19:56 UTC) — Attacker logged into a further compromised engineer’s machine, used stolen credentials, and deployed a container that gave access to the internal wallet signing service.

The attacker then used unauthorized access to the wallet signing service to initiate transactions outside the normal withdrawal flow.

Assets Moved and EIP-7702 Mechanism

Between 20:05 and 20:09 UTC, five hot wallets sent 233.46 million XRP. Additional hot wallets on Solana and Optimism sent approximately 970,500 SOL and 44.2 million OP. A further transfer of 18,270 BTC followed.

On Ethereum the attacker exploited EIP-7702 (an authorization mechanism that lets an account delegate certain execution rights to a smart contract without exposing the private key). They submitted 50 signing transactions to establish malicious on-chain delegations. These authorizations continued to allow asset movement even after Binance suspended withdrawals, because the delegations lived on-chain and the hot wallet used Multi-Party Computation (MPC) — there was no single private key that could instantly revoke them.

The final unauthorized transfer of 2,961.9 ETH finalized at 23:56 UTC. At 00:10 UTC on 30 October, Binance cleared the EIP-7702 delegation by authorizing the zero address from the affected hot wallet. No further unauthorized transfers were observed after that point.

Binance has repeatedly stated it found no evidence that any wallet private keys were leaked.

User Protection and Recovery Status

Binance’s co-CEOs (Yi He and Richard Teng) confirmed that customer assets were held under the exchange’s normal security architecture (majority in cold storage) and were not impacted. The compromised assets belonged to Binance’s own hot-wallet operations.

  • More than USD 6.34 billion set aside in company funds (including ~USD 5 billion already held in the exact impacted tokens: USDC, USDT, BTC, ETH, BNB, etc.).
  • As of 31 October 2026, 98% of impacted token assets had been replenished and were verifiable on the Proof of Reserves page. Remaining illiquid assets were being purchased.
  • Approximately USD 2.85 billion frozen or intercepted through coordination with law enforcement, blockchain intelligence firms, token issuers, and partners.
  • Withdrawals were temporarily suspended for security checks and have since resumed in phases across networks.

Binance has also published updated Proof of Reserves snapshots so users can independently verify backing.

Attribution and Broader Context

The Federal Bureau of Investigation has publicly stated that the Democratic People’s Republic of Korea is responsible for the incident, linking it to the TraderTraitor activity previously associated with other large cryptocurrency thefts. Binance has cited this FBI information in its official updates.

Richard Teng described the event as “one of the most sophisticated attacks the digital asset industry has ever seen” and noted that it was a prolonged campaign rather than a single point of failure.

Frequently Asked Questions (Based on Official Statements)

Were user funds lost?

No. Binance has stated it will absorb the full financial impact through SAFU and corporate treasury. User assets were not affected by the hot-wallet compromise.

Was a private key leaked?

Binance has found no evidence of any wallet private-key leak. The attacker gained unauthorized access to the internal signing service.

How much was frozen?

Approximately USD 2.85 billion has been frozen or intercepted (figures subject to reconciliation and market volatility).

Has the incident been fully resolved?

Entry points were closed, affected systems rebuilt, and withdrawals restored in phases. Investigation continues and independent security reviews are underway. A full technical post-mortem is expected once verification is complete.

Summary and Industry Lessons

The 29 October 2026 Binance incident was a multi-stage campaign that culminated in unauthorized use of an internal wallet signing service, including EIP-7702 delegations on Ethereum. Official statements confirm no private-key compromise of user wallets, full coverage of losses by Binance, substantial asset freezes, and rapid replenishment verified via Proof of Reserves.

For developers and operators building wallet infrastructure, signing services, or hot-wallet systems, the case underscores the importance of device controls, least-privilege access, anomaly detection on signing flows, and careful handling of advanced account-abstraction features such as EIP-7702.

Key Takeaway

Binance covered the ~USD 6.34 billion impact itself; user funds remained protected. The attack path involved months of social engineering and tool compromise rather than a simple key theft.


Building secure Web3 or wallet infrastructure?

I work on production Next.js, smart-contract interfaces, and secure on-chain systems. Get in touch or explore services.

Portrait of Mussawar Hayat

Written by

Mussawar Hayat

Next.js & Web3 Full-Stack Developer

I build production SaaS platforms, dashboards and smart-contract front ends with Next.js, TypeScript, PostgreSQL and Solidity, working remotely with teams in North America and Europe. The guides here come from problems I've solved on client and personal projects.