Skip to main content
Hashbeam

Crypto protocols, markets and policy

3c8b51

Binance details EIP-7702 role in $6.34B theft

Binance says attackers used internal signing access and Ethereum’s EIP-7702 delegation to move $6.34 billion; it reports 98% of affected assets replenished.

The Hashbeam Desk··3 min read

Binance details EIP-7702 role in $6.34B theft

Binance says attackers used unauthorized access to its internal wallet signing service and Ethereum’s EIP-7702 authorization mechanism to move about $6.34 billion in assets on Oct. 29, making the incident the largest reported crypto theft. In its initial findings report published Nov. 3, the exchange said 98% of affected token assets had been replenished as of Oct. 31 and could be verified through its Proof of Reserves page. The investigation is ongoing, and Binance said independent cybersecurity firms will review its findings.

How did the attackers use EIP-7702?

They used the Ethereum account-delegation mechanism to give an attacker-controlled smart contract partial execution rights over a Binance hot wallet, the exchange said. EIP-7702 allows an account to delegate certain execution rights to a contract without exposing its private key. Binance says the attackers first gained unauthorized access to an internal signing service, then used it to initiate transactions outside the normal withdrawal process.

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 also reported transfers of about 970,500 SOL from hot wallets on Solana and 44.2 million OP on Optimism, followed by an 18,270 BTC transfer. On Ethereum, the attacker used the signing service to establish the malicious delegation. Binance says attackers submitted 50 signing transactions to manipulate the account nonce and set up those authorizations.

The delegation mattered because it existed on-chain and could keep authorizing asset movements independently of Binance’s normal withdrawal infrastructure. Suspending withdrawals therefore did not invalidate it. Binance says the hot wallet used multi-party computation (MPC), so no single private key was available to revoke the authorization immediately. The exchange had to execute a separate revocation procedure; a final unauthorized transfer of 2,961.9 ETH settled at 23:56 UTC, and Binance says it cleared the delegation at 00:10 UTC on Oct. 30.

What did Binance confirm about the breach?

Binance’s initial explanation pointed to a compromised DevOps engineer’s laptop that gave an attacker access to a service container. Its later report describes a broader, multi-stage intrusion involving social engineering through fake recruitment interviews, malicious software, compromised internal AI tooling, endpoint access and the signing service. Binance says it found no evidence that wallet private keys were leaked. The additional access points and the full sequence remain under investigation.

That distinction matters: Binance’s account describes misuse of systems able to initiate or authorize withdrawals, not a disclosed break of the cryptography protecting wallet keys. The exchange says it has closed identified entry points, rebuilt or replaced systems touched in the attack path, and tightened device and wallet-service controls. It also says some technical details will remain confidential while the investigation continues.

Who does the FBI identify, and what has been recovered?

The FBI attributes the theft to North Korea and calls the operation TraderTraitor. In its Oct. 31 alert, the bureau said investigators had observed the actors converting stolen assets primarily into Ether and urged crypto services and infrastructure operators to block transactions tied to listed addresses. Binance says about $2.85 billion in assets had been frozen or intercepted as of its Nov. 3 report; that figure is subject to reconciliation and market-price volatility.

Binance says it will absorb the financial impact and had set aside more than the amount required to cover the loss. Its report says 98% of affected token assets had been replenished by Oct. 31, with the remaining, less liquid assets still being purchased. Those are Binance’s reported remediation figures; its report calls itself preliminary, and an independent review is pending.

References