• Home
  • Binance Suffers $6.4 Billion Wallet Breach - How Attackers Bypassed Controls

Binance Suffers $6.4 Billion Wallet Breach – How Attackers Bypassed Controls

A computer server rack beside an open padlock, surrounded by scattered gold coins.

Binance Encounters $6.4 Billion Wallet Breach – How Compromised Signing Infrastructure Evaded Internal Emergency Controls

Key Takeaways

  • Attackers obtained credentials to wallet signing infrastructure after a months-long social engineering campaign.
  • Approximately $6.4 billion in cryptocurrency was transferred to unauthorized addresses.
  • Emergency withdrawal suspensions failed to stop on-chain permissions established through the Ethereum EIP-7702 mechanism.
  • The attackers converted $325 million in stablecoins into other assets within 20 minutes to prevent issuer freezes.

Social engineering campaigns compromised internal employee systems over several months

The security incident began long before the actual unauthorized transfers took place. Binance detected an anomaly in June when an engineer downloaded a tampered artificial intelligence coding tool. The exchange replaced the affected device immediately. The attackers had already managed to gather actionable intelligence regarding internal employees and network infrastructure.

Another engineer encountered a fictitious recruitment process in September. The attackers used interviews and a malicious coding assignment to penetrate the system further. They accessed additional machines by October 20 using compromised employee systems and internal AI tools. This lateral movement ultimately yielded credentials that unlocked the wallet signing infrastructure.

Accessing the signing infrastructure gave the attackers the ability to authorize transactions directly. They bypassed the ordinary withdrawal mechanisms entirely. This direct control set the stage for the massive asset transfer that commenced later that month.

alert-circle
You can also find us on Telegram: Click here to follow our Telegram channel.

Malicious on-chain delegations outlived internal withdrawal suspensions

The large-scale theft began on October 29. Attackers initiated transfers from hot wallets between 20:05 and 20:09 UTC. They moved roughly 223.46 million XRP, 970,500 SOL, and 44.2 million OP to addresses under their control. Bitcoin and Ethereum transfers quickly followed. Chainalysis estimates the total value of the stolen assets at $6.4 billion.

Attackers utilized the EIP-7702 mechanism on the Ethereum network to establish lasting control over the funds. This protocol allows an externally owned account to delegate execution rights to smart-contract code. The compromised signing infrastructure granted these execution rights over a Binance hot wallet. The attackers executed 50 signed transactions to manipulate account nonces and secure the delegation.

Binance responded by suspending normal withdrawals and shutting down affected services. This internal emergency switch failed to terminate the on-chain permissions established through EIP-7702. The Ethereum network continued to recognize the attacker’s delegation until it was explicitly revoked. Pausing internal software does not automatically erase permissions already written to a decentralized blockchain.

Multi-party computation architecture extended the timeline for revoking permissions

The exchange utilized multi-party computation to secure its hot wallets. This architecture distributes cryptographic signature production across multiple components instead of relying on one single private key. This structure prevents single points of failure under normal circumstances. It also meant no single private key existed to immediately cancel the malicious delegation once the breach was detected.

Engineers at Binance had to develop a specialized revocation procedure while the attack was actively happening. Creating this specific procedure took valuable time and prolonged the unauthorized asset movement. The final unauthorized Ethereum transfer of 2,961.9 ETH was confirmed on-chain at 23:56 UTC.

Binance successfully cleared the malicious EIP-7702 delegation at 00:10 UTC on October 30. The engineers implemented a new authorization directed to the zero address. The company reported a 98% replenishment of the affected holdings by November 4 using its own financial resources.

Internal deposit systems continued directing funds into compromised wallets

Containment efforts faced an additional operational challenge during the incident. Binance’s deposit-consolidation system kept funneling newly deposited customer assets into a compromised Ethereum wallet. This specific address, identified as Binance 14, allowed the attacker to sweep arriving assets instantly.

Nexus Mutual reconstructed a sequence demonstrating the speed of these secondary thefts. The attacker swept 200 million USDT at approximately 21:44 UTC. Another Binance-labeled wallet had deposited those exact funds just 72 seconds earlier.

This internal routing issue presents a distinct security challenge separate from the EIP-7702 exploit. Operators must interrupt automated internal asset flows while simultaneously fighting to revoke on-chain authority. Securing the perimeter requires stopping both outgoing unauthorized transfers and incoming automated deposits.

Attackers executed rapid asset swaps to evade stablecoin issuer freezes

Stolen assets that leave an exchange’s immediate control trigger a containment race between investigators and attackers. Centralized stablecoin issuers like Tether and Circle maintain the ability to freeze specific tokens at designated addresses. Decentralized assets like Bitcoin and Ethereum lack equivalent central authorities with freezing capabilities.

The attackers attempted to move approximately $500 million in stablecoins through a swapping address. They successfully converted around $325 million into assets less susceptible to issuer freezes within roughly 20 minutes. Moving funds into Ether placed them beyond the reach of centralized stablecoin blacklists.

The remaining $175 million in stablecoins was successfully frozen by the issuers. This sequence highlights the extreme time sensitivity involved in post-breach asset recovery. Attackers prioritize liquidating centrally controlled tokens immediately to secure their illicit gains.

Our Assessment

This incident demonstrates that internal security controls cannot fully override decentralized on-chain permissions. Exploiting mechanisms like EIP-7702 allows attackers to establish persistent authority that survives standard emergency withdrawal pauses. The breach highlights a structural tradeoff within multi-party computation systems, where distributed security can inadvertently slow down emergency revocation procedures. Exchanges face complex challenges in halting automated internal fund routing during an active intrusion. The rapid conversion of stablecoins to decentralized assets confirms that attackers understand and exploit the operational limitations of central issuer freezes.

We have imposed strict editorial guidelines on ourselves and explain our testing methods openly and comprehensively. We also communicate transparently how our work is financed. This site may contain tracking links, but this does not influence our objective view in any way.

Latest News

Isabella Brown

About the author

Isabella Brown

Isabella Brown is a Senior Editor and Crypto Gambling Analyst at KryptoCasinos.com. She has worked in iGaming since 2017, including three years analyzing industry news and trends at iGaming Business (iGB). She covers crypto gambling regulation, casino security, and market developments for US readers, and checks site content for accuracy before publication.
🍪
We use cookies. By using this site, you accept them.