Ethereum’s shortcut to sensible pockets conduct arrived with a brand new belief downside: a pockets could make an everyday deal with programmable with out transferring the consumer’s belongings, whereas the delegated code beneficial properties energy to behave with that account’s authority.
A peer-reviewed examine launched for USENIX Safety ’26 discovered that attacker-linked contracts have been related to 2,322,548 of the three,664,166 EIP-7702 authorization transactions it noticed throughout seven chains via July 15, 2025. That’s 63% of the historic transaction quantity within the researchers’ dataset.
The authors tied a comparatively small set of malicious contracts to repeated authorizations and described some attacker-controlled exercise as possible apply or proof-of-concept testing throughout an early, exploratory part.
The determine measures transactions, whereas distinct-wallet prevalence and the present 2026 assault fee sit exterior the examine’s scope.
Why attackers dominated the early authorization rely
Ethereum activated Pectra, together with EIP-7702, on Could 7, 2025. The ultimate specification launched a type-4 transaction that lets an externally owned account set a pointer to deployed contract code.
The deal with stays the identical, the unique personal key retains management, and calls to the account can execute the delegated code within the account’s context.
That design can provide a standard pockets options related to sensible accounts, together with batched calls and sponsored transactions, with out forcing the consumer emigrate to a brand new deal with. It additionally turns the delegation goal into pockets infrastructure.
Buggy or hostile code could possibly make approvals, transfers and utility calls because the account.
It says functions shouldn’t anticipate to ask customers for arbitrary authorization signatures as a result of there isn’t a secure generic interface for customers to evaluate code with unrestricted account entry. Wallets are anticipated to vet the implementation.
Attackers might put together authorization fields off-chain and ask a sufferer to signal, and a pockets would possibly scale back the choice to a high-level account-upgrade immediate whereas obscuring the contract deal with or code receiving authority.
The protocol verifies the account proprietor’s signature, whereas the pockets nonetheless has to ascertain whether or not the chosen code deserves management.
The researchers analyzed greater than 22.8 billion historic transactions on Ethereum, Binance Good Chain, Polygon, Optimism, Arbitrum, Base, and Gnosis.
Inside that information, they examined 3,664,166 EIP-7702 authorizations via the cutoff and used transaction filters, bytecode evaluation and handbook assessment to determine 924 malicious contracts. They categorised 793 as EOA-targeted, 124 as contract-account-targeted and 7 as composite assaults.
Research measureWhat it captures3,664,166 authorizationsHistorical EIP-7702 transactions throughout seven chains via July 15, 20252,322,548 authorizations, or 63percentHistorical transactions related to malicious EOA-targeted contracts924 malicious contractsThe detected and manually reviewed set below the researchers’ methodology$2.36 millionDetected realized loss throughout three assault categoriesAbout $10.14 millionPotential publicity in a separate legacy-contract subset
The paper says malicious contracts have been reused disproportionately, so transaction counts can rise a lot quicker than the variety of distinct contracts or affected customers. In a younger authorization market, that repeated attacker exercise had an outsized impact on the denominator.
Attackers discovered a repeatable path to account-level authority earlier than wallets had made the belief determination as legible and constrained as the ability it conveyed.
The chance reaches past hijacked wallets
The examine measured $2,362,848.76 in realized losses throughout its three assault classes. A separate estimate coated older contracts whose defenses assumed that programmable EOAs couldn’t exist.
EIP-7702 breaks the previous assumption that msg.sender == tx.origin reliably identifies a plain EOA or blocks contract-mediated conduct.
The researchers recognized 967 energetic Ethereum contracts in a subset utilizing that examine as a flash-loan protection and estimated that about $10.1 million in belongings have been at potential excessive threat.
Detected theft totaled about $2.36 million, so the $10.14 million represents belongings uncovered by a defensive assumption that not held.
The researchers noticed attackers rebinding accounts to benign code after an assault, making current-state-only monitoring unreliable. In addition they discovered 500 particular nonzero delegation targets with no deployed code.
A precomputed CREATE2 deal with might obtain code later, altering what the account executes whereas the recorded goal stays the identical.
These patterns make authorization historical past a part of the safety boundary. Wallets and monitoring instruments want to recollect the place an account beforehand pointed, consider modifications in delegated code, and deal with an undeployed goal as unresolved relatively than innocent.
The authors’ guidelines might miss malicious contracts earlier than preparation transactions develop into seen or assaults utilizing novel interfaces exterior the strategy’s protection. The 924 contracts are the detected and manually verified set, whereas the full universe of abuse stays unknown.
Protected default conduct begins with making delegation a wallet-controlled set up determination. Put up-study ethereum.org steering requires whitelisting delegation contracts, prominently displaying the goal, avoiding arbitrary delegation on {hardware} wallets, and counting on audited implementations.
An account-abstraction pockets functionality proposal takes the identical course, calling for a strict shortlist of well-known, publicly audited sensible account implementations. These paperwork don’t measure how persistently manufacturing wallets have adopted it.
Functions ought to request the characteristic they want and go away the account implementation to the pockets. For an approval and swap in a single stream, present Ethereum Basis steering factors builders to a pockets interface corresponding to ERC-5792.
The pockets can then select EIP-7702, ERC-4337, or one other account system with out asking the consumer to approve low-level delegation code chosen by the appliance.
Present steering recommends signing initialization parameters or limiting setup to the ERC-4337 EntryPoint, closing a front-running path by which an attacker substitutes their very own values.
The examine recognized a associated failure mode in legacy pockets code: constructors don’t run once more when an account delegates to an present contract, which may go away possession unset and externally claimable.
A benign present pointer can not erase a malicious historical past, and a goal with no code might purchase conduct later. Wallets want sturdy authorization data, clear alerts when the delegation modifications, and a elimination path that customers can perceive.
Making the EIP-7702 pockets programmability secure by default requires wallets to deal with delegation as set up of the account’s management aircraft: prohibit who can request it, expose precisely what is going to management the account, confirm the way it initializes, and hold watching after the pointer modifications.
