Live News

Binance Pledges Full Reimbursement After $6.3 Billion Exploit Leverages Ethereum Account Abstraction Feature

Binance Pledges Full Reimbursement After $6.3 Billion Exploit Leverages Ethereum Account Abstraction Feature

Binance committed on Friday to cover all customer losses after attackers drained roughly $6.3 billion from its platform, staging the largest theft in the history of the digital asset industry. While investigators point to compromised transaction-signing infrastructure as the root mechanism of the intrusion, analysts also found that the attackers capitalized on Ethereum’s EIP-7702 standard to sweep funds in rapid succession.

Compromised Infrastructure and Bypassed Controls

The breach extends far beyond a single compromised workstation. Although early inquiries focused on a compromised laptop owned by an exchange engineer, Binance confirmed in an update on X that internal reviews revealed multiple entry points across its network.

Crucially, the exchange maintains that cryptographic secrets were not directly exposed. Binance chief executive Richard Teng stated on X that investigators have uncovered no proof that hot wallet private keys were exfiltrated.

Instead, the attack trajectory indicates that the perpetrators penetrated Binance’s internal pipeline until they could feed unauthorized transaction requests directly into a valid hot wallet signer. Once the signing architecture approved the malicious requests, the funds moved. Blockchain security firm Blockaid observed that while the compromised signing pipeline served as the primary failure point, Ethereum’s newly implemented EIP-7702 specification gave the hackers a mechanism to route past normal withdrawal tripwires and empty addresses simultaneously.

The Mechanics of EIP-7702

Ethereum core developers activated EIP-7702 in May 2025 alongside the broader Pectra hard fork. The proposal allows standard externally owned accounts (EOAs) to temporarily adopt smart contract capabilities, enabling batch transactions, delegated logic, and sponsored gas payments without requiring users to migrate permanently to contract-based smart accounts.

The feature had drawn scrutiny long before the Binance incident. Ethereum community researcher VEER pointed to technical warnings raised during network discussions in 2024, noting that while the Binance breach required much broader network penetration than a single forged signature, EIP-7702 handed the intruders “a handy sweep button on Ethereum.”

Exploitation of the standard began almost immediately after its rollout. Crypto market maker Wintermute documented that within weeks of Pectra’s activation in May 2025, the majority of active EIP-7702 delegations routed to predatory smart contracts engineered to siphon balances from compromised keys. Subsequent incidents followed in September 2025, when holders of World Liberty Financial (WLFI) tokens suffered unauthorized asset drains through delegated contract executions.

Debate Over Protocol Versus Operational Failures

Wallet developers caution against viewing EIP-7702 as the root cause of the exploit. Ivo Georgiev, co-founder and chief executive of Ethereum wallet provider Ambire, argued that the attackers already possessed the authorization necessary to move exchange reserves, meaning the theft would have proceeded regardless of the standard used.

Georgiev emphasized that the standard’s real hazard lies in post-incident response. Once an account delegates authority to an external contract under EIP-7702, that authority persists until explicitly revoked. If exchange security teams patch the original intrusion without revoking the active delegations on-chain, attackers can retain persistent drainage routes.

“This is a problem with EIP 7702, it’s just very very poorly understood,” Georgiev said.

Blockaid warned that the attack vectors exposed at Binance pose a systemic threat to custodial platforms across the sector, advising exchanges to implement pre-execution transaction simulations to intercept uncharacteristic authorization payloads before automated signers broadcast them to the mempool.

Tags:
Share:

Related Post