Ethereum’s shortcut to good pockets conduct arrived with a brand new belief drawback: a pockets could make a daily handle programmable with out shifting the person’s belongings, whereas the delegated code positive factors energy to behave with that account’s authority.
A peer-reviewed research launched for USENIX Safety ’26 discovered that attacker-linked contracts had 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 relatively small set of malicious contracts to repeated authorizations and described some attacker-controlled exercise as probably observe 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 outdoors the research’s scope.
Why attackers dominated the early authorization rely
Ethereum activated Pectra, together with EIP-7702, on Might 7, 2025. The final specification launched a type-4 transaction that lets an externally owned account set a pointer to deployed contract code.
The handle 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 traditional pockets options related to good accounts, together with batched calls and sponsored transactions, with out forcing the person emigrate to a brand new handle. It additionally turns the delegation goal into pockets infrastructure.
Buggy or hostile code might be able to make approvals, transfers and utility calls because the account.
It says functions mustn’t count on to ask customers for arbitrary authorization signatures as a result of there is no such thing as a protected 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 cut back the choice to a high-level account-upgrade immediate whereas obscuring the contract handle 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 knowledge, they examined 3,664,166 EIP-7702 authorizations via the cutoff and used transaction filters, bytecode evaluation and guide assessment to determine 924 malicious contracts. They categorised 793 as EOA-targeted, 124 as contract-account-targeted and 7 as composite assaults.
| Examine measure | What it captures |
|---|---|
| 3,664,166 authorizations | Historic EIP-7702 transactions throughout seven chains via July 15, 2025 |
| 2,322,548 authorizations, or 63% | Historic transactions related to malicious EOA-targeted contracts |
| 924 malicious contracts | The detected and manually reviewed set underneath the researchers’ methodology |
| $2.36 million | Detected realized loss throughout three assault classes |
| About $10.14 million | Potential publicity in a separate legacy-contract subset |
The paper says malicious contracts had been reused disproportionately, so transaction counts can rise a lot sooner 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 resolution as legible and constrained as the facility it conveyed.
The chance reaches past hijacked wallets
The research 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 outdated 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 had 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 handle 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 adjustments 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 turn into seen or assaults utilizing novel interfaces outdoors the tactic’s protection. The 924 contracts are the detected and manually verified set, whereas the whole universe of abuse stays unknown.
Protected default conduct begins with making delegation a wallet-controlled set up resolution. Put up-study ethereum.org guidance requires whitelisting delegation contracts, prominently displaying the goal, avoiding arbitrary delegation on {hardware} wallets, and counting on audited implementations.
An account-abstraction wallet capability proposal takes the identical path, calling for a strict shortlist of well-known, publicly audited good 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 circulation, present Ethereum Foundation steering factors builders to a wallet interface resembling ERC-5792.
The pockets can then select EIP-7702, ERC-4337, or one other account system with out asking the person 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 wherein an attacker substitutes their very own values.
The research recognized a associated failure mode in legacy pockets code: constructors don’t run once more when an account delegates to an current contract, which may go away possession unset and externally claimable.
A benign present pointer can’t 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 adjustments, and a elimination path that customers can perceive.
Making the EIP-7702 pockets programmability protected by default requires wallets to deal with delegation as set up of the account’s management aircraft: limit who can request it, expose precisely what’s going to management the account, confirm the way it initializes, and maintain watching after the pointer adjustments.
