Binance Security Breach: Unraveling the $6.3 Billion Wallet Exploit
The recent breach at Binance has unveiled the tactics employed by an attacker who utilized a single successful authorization from an Ethereum wallet to seize control of a major exchange wallet. Binance estimates that the security incident on October 29 has affected roughly $6.3 billion in cryptocurrency.
Summary
- Binance estimates that the October 29 security incident involved approximately $6.3 billion in cryptocurrency.
- Blockaid traced the hack to 50 EIP-7702 authorizations, with one successfully breaching the Binance 14 hot wallet.
- Initial investigations by Binance indicate that a compromised DevOps engineer’s laptop may have been the initial access point, although no leaked private key has surfaced.
- Tether and Circle have frozen over $2.3 billion in stablecoins associated with the breach, while Binance reported about $3 billion in frozen assets.
- During security assessments, Binance temporarily suspended deposits and withdrawals and assured that it would tap into its SAFU fund and company reserves to cover losses.
According to Blockaid, the hacker exploited Ethereum’s EIP-7702 authorization characteristic to redirect Binance’s widely used Binance 14 hot wallet to a harmful smart contract. The attacker executed 50 authorizations in a single transaction, with just one matching the wallet’s transaction counter, thereby successfully executing the contract.
On October 30, Binance’s security update suggested that a possibly compromised DevOps engineer’s laptop was the breach source. The exchange disclosed that around $3 billion in affected assets had been frozen, assuring customers that their losses would be compensated.
Binance hack involved 50 authorizations to seize control of hot wallet
Blockaid’s investigation pinpointed an Ethereum transaction at 20:20:59 UTC on October 29 that involved 50 EIP-7702 authorizations targeted at Binance 14.
EIP-7702 allows standard Ethereum wallets to delegate transaction execution to smart contract code. Each authorization must correspond to the wallet’s current nonce, which serves as a transaction counter that changes as accounts conduct transactions.
As Binance 14 was in the process of handling withdrawals, the attacker couldn’t accurately predict its nonce. The authorizations submitted contained consecutive values ranging from 18,914,775 to 18,914,824, increasing the chances that one would correctly align during Ethereum’s transaction processing.
Only one authorization was successful, redirecting the wallet to an unverified contract which permitted an address controlled by the attacker to execute a function called sweep(), transferring ETH and ERC-20 tokens while reserving 1 ETH for transaction fees.
This unauthorized delegation could have influenced subsequent deposits until Binance acted to revoke it. The exchange later confirmed that it had invalidated the affected authorization.
Previous EIP-7702 wallet attacks have demonstrated similar weaknesses, including one on October 14 where a compromised Ethereum account suffered a loss of about $22,770 in ETH.
Binance notes laptop compromise may have facilitated unauthorized withdrawals
Preliminary investigations by Binance indicated that a DevOps engineer’s laptop might have been compromised, enabling the attacker to access an internal service container necessary for executing withdrawal transactions.
Despite the lack of evidence regarding any compromised wallet private key, the exact method the attacker used to secure the needed authorizations for redirecting Binance 14 remains unknown.
Blockchain analysis by Blockaid uncovered that preparations for the theft started before the incident, with the attacker funding an operational address through three withdrawals from Tornado Cash and deploying the malicious contract several hours prior to targeting Binance.
At around 20:24 UTC, the attacker successfully drained Binance 14 of cryptocurrency valued at approximately $2.5 billion, which included 167,464 ETH, over 1.6 billion USDT, and various other tokens.
Further transfers were executed from Binance 16 and another Ethereum hot wallet that held USDC. The operation spanned multiple blockchain networks, including Bitcoin, Tron, Arbitrum, and Avalanche.
Earlier investigations into unauthorized wallet delegations found automated contracts that transferred assets from hacked accounts following Ethereum’s Pectra upgrade.
Tether and Circle freeze billions connected to the Binance breach
In the wake of the hack, various cryptocurrency issuers began to restrict access to assets linked to suspicious addresses.
Tether’s CEO, Paolo Ardoino, confirmed that the issuer of the stablecoin had frozen over 1.567 billion USDT related to the suspected breach. Circle’s CEO, Jeremy Allaire, reported that more than 800 million USDC had been frozen while collaborating with law enforcement.
Jack McDonald, Ripple’s head of stablecoins, indicated that the company is working with relevant parties to freeze affected RLUSD assets.
Additionally, the Arbitrum Security Council disclosed that 74,559,805 ARB and 8,425 ETH were transferred from an address linked to the hack to a controlled intermediary wallet, with the assets only allowed to move upon further council intervention or an Arbitrum DAO governance decision.
This coordinated effort led to approximately $3 billion being frozen across affected assets, based on the latest estimates from Binance.
Binance commits to covering losses as investigation progresses
Throughout ongoing security measures, Binance temporarily suspended deposits and withdrawals, working together with blockchain intelligence firms and law enforcement.
The exchange announced that it would leverage its Secure Asset Fund for Users (SAFU) alongside internal funds to mitigate losses. An updated Proof of Reserves will be shared following the completion of remediation efforts.
Binance founder Changpeng Zhao publicly acknowledged the suspected breach, asserting, “User funds are safe!” He emphasized that although he no longer manages the exchange, he expects customers to be fully compensated.
Meanwhile, Binance’s U.S. affiliate confirmed that its operations remained unaffected by the incident.
The exchange indicated that its investigation team is diligently working to clarify how the attacker penetrated its internal systems and obtained wallet authorizations. A detailed technical post-mortem will be published once the investigation is complete.
