Skip to content
Finality

Crypto protocol and market news

Binance says EIP-7702 wallet attack moved $6.34 billion

Binance says attackers used its wallet signing service and EIP-7702 delegations to move $6.34 billion; it reports freezing $2.85 billion and replenishing 98% of assets.

The Finality Desk3 min read#aeea09

Binance says EIP-7702 wallet attack moved $6.34 billion

Binance says attackers used unauthorized access to its internal wallet signing service to move about $6.34 billion in digital assets on Oct. 29, including through malicious EIP-7702 delegations that remained active after withdrawals were suspended. The exchange’s initial incident report says roughly $2.85 billion has been frozen or intercepted, and that Binance will cover the loss rather than pass it to users. The Binance incident update describes a signing-service compromise that bypassed the normal withdrawal process and enabled on-chain transfers across several networks.

The scale and response differ from the first reports. The Associated Press reported that Binance initially described a potential security issue and an estimated $6.3 billion impact, while saying it had found no evidence of a wallet private-key leak. Binance’s Nov. 3 update now calls the assets stolen and gives a more detailed account of the transaction path. Its figures remain subject to reconciliation and market-price volatility.

How did the attacker get transactions signed?

Binance says the attacker gained unauthorized access to its internal wallet signing service and initiated transactions outside the normal withdrawal process. The exchange’s account of the preparation describes social engineering, malware delivered through a fake job interview assignment, and compromised internal systems. Binance says investigators believe the attacker later used stolen credentials to deploy a container and trigger a malicious script.

On Oct. 29, five Binance hot wallets sent 233.46 million XRP to an attacker-controlled address between 20:05 and 20:09 UTC. Binance hot wallets on Solana and Optimism also sent about 970,500 SOL and 44.2 million OP. A Binance hot wallet later sent 18,270 BTC. The incident report says an internal alert for large-volume transfers prompted the exchange to investigate.

Why did suspending withdrawals fail to stop the transfers?

The attacker used Ethereum’s EIP-7702 authorization mechanism to give an attacker-controlled smart contract partial execution rights over a Binance hot wallet. EIP-7702 lets an account delegate specified execution rights to a contract without exposing its private key. Binance says the attacker submitted 50 signing transactions to manipulate the account nonce and establish malicious delegation authorizations.

Those authorizations existed on-chain, so they could continue enabling asset movements independently of Binance’s normal withdrawal infrastructure. Suspending withdrawals and shutting down hot-wallet services did not automatically invalidate them. The exchange says its wallet used multi-party computation (MPC), meaning there was no single private key it could use to revoke the authorizations immediately; it had to develop and execute a specialized revocation procedure.

What has Binance recovered and replaced?

Binance says about $2.85 billion in assets have been frozen or intercepted through coordination with blockchain partners, issuers and law enforcement. Its update says the final unauthorized transfer, 2,961.9 ETH, finalized on-chain at 23:56 UTC on Oct. 29. At 00:10 UTC the next day, Binance executed a new authorization from the Binance14 hot wallet to the zero address, clearing the EIP-7702 delegation code.

Binance also says that, as of Oct. 31, it had replenished 98% of impacted token assets and set aside more than the amount needed to cover the loss. It is still purchasing the outstanding, less-liquid assets. The exchange has rebuilt or replaced systems in the attack path and says an independent cybersecurity review is underway. Its investigation remains open, so the account of the intrusion and the impact figures may change.

Sources and documents