On October 29, 2026, an Ethereum hot wallet belonging to Binance was emptied in a single transaction.
The tool behind the drain was EIP-7702, a feature that went live on Ethereum in May 2025.
As of October 30, 2026, no flaw in EIP-7702 itself has been reported.
It did exactly what a valid signature told it to do, and that is the part worth understanding.
Key Takeaways
EIP-7702 lets a regular Ethereum wallet run smart contract code, and it went live on May 7, 2025.
A token approval covers one token for one app, while an EIP-7702 delegation hands a contract your whole account.
Every delegation needs the wallet's own signature, so the Binance hack looks like a signing-side failure, not an Ethereum bug.
Exchange users should watch official notices, withdrawal status, proof of reserves and the post-mortem.
Self-custody users only face EIP-7702 risk if they signed a delegation, which Etherscan's Delegated Address field shows.
A delegation can be reset to the zero address, but if you don't remember signing it, treat the wallet as compromised.
EIP-7702 is an Ethereum upgrade that lets a regular crypto wallet, known as an externally owned account or EOA, borrow smart contract code and behave like a smart account. Each one names a contract and must be signed with the wallet's own private key.
It starts with a signature.
You sign an authorization that names a contract, the chain it covers and your account's nonce, which is simply a running count of your transactions. Any account can then submit that authorization to Ethereum, which is how a third party can pay the fee for you.
Once it lands, the network writes a small pointer on your account, which the specification calls a delegation indicator.
From then on, calls to your address run the code of the contract it points to, while your private key keeps full control of the account.
To undo it, you sign a new authorization that points to the zero address, and the account goes back to being a plain wallet.
Account abstraction is the push to make Ethereum wallets programmable instead of limited to one signature and one action at a time.
EIP-7702 brings that idea to existing wallets, so nobody has to move funds to a new address.
The specification names three uses:
Batching: several actions, such as approve and swap, in one all-or-nothing transaction
Sponsorship: another account pays the network fee for you and can be repaid in a token other than ETH
Privilege de-escalation: a sub-key with narrow permissions, such as spending tokens but not ETH
Each of these depends on the contract your wallet points to, which is why the next section matters.
A token approval lets one app move one token, usually up to a set amount.
An EIP-7702 delegation hands the logic of your entire account to a contract, covering every asset inside it, until you reset it.
That gap in scope is why a bad delegation does far more damage than a bad approval.
Think of your wallet as a house.
A token approval is like handing someone the key to one cabinet to take out one item.
An EIP-7702 delegation is closer to hiring a house manager who runs every room.
A good manager, like a reputable wallet app's smart account contract, only follows your instructions.
A malicious one can clear out the whole house in one trip.
Your private key stays the master key, which also means anyone holding it can hire a new manager.
On October 29, 2026, an attacker used signed EIP-7702 authorizations to point Binance's Ethereum hot wallet at the attacker's own contract.
Minutes later, one transaction emptied it.
Early on-chain estimates put losses across Binance's wallets in the billions of dollars as of October 30, 2026.
Public on-chain data shows four steps:
Sign: Around 20:20 UTC, a batch of authorizations signed with the wallet's key landed on Ethereum.
Point: The wallet's nonce kept changing, so the batch reportedly covered many values, and the one that matched handed the wallet to the attacker's contract.
Sweep: About three minutes later, one call moved out ETH, stablecoins and dozens of other tokens.
Reset: Almost four hours later, the delegation was revoked.
Step one is the key detail: a delegation needs the wallet's own valid signature, so either the key itself leaked or a system that holds it signed when it should not have.
As of October 30, 2026, Binance had not published a root cause.
Two explanations are on the table, pointing to very different weak spots.
The first is a leaked private key, a familiar failure with a familiar fix: retire the key and lock down everyone who had access.
The second is more unsettling.
Many exchanges route hot wallet signing through automated services that check where funds are going and how much is moving. An EIP-7702 authorization is not a normal transfer.
It is a short signed message naming a contract, with no recipient or amount for those rules to inspect.
If a signing service approved one without decoding it, the exchange's own security layer signed away control of the wallet.
Early reports also described funds leaving on blockchains that have no EIP-7702 feature at all, which, if confirmed, would point to the signing side.
A hot wallet is only the slice of an exchange's funds kept online for withdrawals.
Whether customers are made whole depends on the exchange's reserves and what it formally commits to, such as a protection fund, so trust official updates over social media posts. Watch for:
Announcements on Binance's own website and verified accounts
Deposit and withdrawal status for each network
An updated proof of reserves report
A post-mortem that names the root cause and the fix
On MEXC, users can confirm their own balance is included in the reserve data through a Merkle tree check.
A hack at one exchange does not automatically put your funds at risk, and moving them is a personal call.
If you do move some, send a small test amount first and double-check the network and address before the full transfer.
Not unless you signed a delegation.
Holding ETH in a self-custody wallet does not switch EIP-7702 on, and there is nothing to "upgrade." The real risk is phishing.
A fake airdrop or website can ask you to sign an authorization that points your wallet at a malicious smart contract, disguised as a routine prompt.
Paste your address into Etherscan and find the Delegated Address field. "Null" means no delegation.
If it shows a contract that isn't your wallet app's, reset it from inside the wallet.
Step 1: A known wallet contract, such as MetaMask's EIP-7702 Delegator, simply means you turned on that wallet's smart account.
Step 2: If you don't recognize the contract, revoke it in your wallet app, which delegates to the zero address.
Step 3: Repeat the check on other EVM chains where you use the same address.
Step 4: If you don't remember signing that delegation, assume your key or seed phrase is exposed and move everything to a new wallet.
Revoking won't rescue a wallet whose key has leaked, because whoever holds the key can sign a fresh delegation a minute later.
EIP-7702 is a finalized, live part of Ethereum, so the feature is not going away.
The clearest fix sits with whoever controls signing: systems that decode every authorization and refuse any contract that isn't pre-approved.
The specification itself says there is no safe way to let apps request delegations freely.
Is EIP-7702 a bug in Ethereum?
No, it is an intended feature with Final status, and every delegation needs the wallet's own signature.
What is the difference between EIP-7702 and ERC-4337?
Both move Ethereum toward account abstraction, but EIP-7702 upgrades an existing wallet while ERC-4337 relies on separate smart contract accounts.
Which Ethereum upgrade added EIP-7702?
EIP-7702 shipped in the Pectra upgrade, which activated on May 7, 2025.
How do I revoke an EIP-7702 delegation?
Sign a new delegation to the zero address from your wallet app, which resets the account to a plain wallet.
Does an EIP-7702 delegation work on other chains?
Only on the chain it names, unless it was signed with chain ID 0, which makes it valid on every EVM chain that supports it.
Was EIP-7702 hacked in the Binance incident?
As of October 30, 2026, no flaw in EIP-7702 had been reported, and the delegation carried the wallet's own valid signature.
Do I need to do anything with my ETH because of EIP-7702?
No, your ETH needs no upgrade, and you only need to act if you find a delegation you don't recognize.
Is my money on Binance safe after the EIP-7702 hack?
As of October 30, 2026, Binance had not published a root cause, so rely on its official announcements and proof of reserves rather than social media posts.
EIP-7702 gives ordinary Ethereum wallets real smart account powers, and it also lets one signature hand over an entire account.
The Binance hack showed that power at full scale, with no Ethereum bug reported as of October 30, 2026.
Check your Delegated Address once, stay wary of any prompt to "upgrade," and follow ETH on MEXC's Ethereum price page.
Related Articles