
Academic paper finds 4,224 contracts that show fake gains during wallet previews, then drain deposits. Ethereum bore 91.5% of $3.48M in losses.
Researchers have identified 4,224 malicious smart contracts that used transaction-simulation tricks to steal roughly $3.48 million from 5,742 victim addresses across Ethereum, BNB Smart Chain, Avalanche and Polygon, according to a July 30 arXiv preprint.
The authors built SimGuard, a contract-bytecode detector, to find the contracts. They linked the contracts to 6,223 victim transactions. Ethereum accounted for 91.5% of the losses. About 83% of the cross-chain total came from the largest inferred cluster of attackers.
The findings have not been peer reviewed. The paper also gives inconsistent figures for its Avalanche contract count and conflicting endpoints for the observation period, leaving its per-chain breakdown and exact time window unresolved.
Transaction simulation takes a pre-signing snapshot of what a transaction is expected to do. The contracts described in the paper contain branches that can produce one result during that check and another when the transaction executes on-chain.
In a storage-control example, the simulation returns the user's deposit plus a tiny reward. An attacker can then change the contract's state, such as by blacklisting the user's address, before the transaction lands. The executed branch sends the deposit to an attacker-controlled address instead.
Timestamp-based contracts can exploit the later block time. Gas-control contracts can behave differently when the simulator and final transaction use different gas limits. Not every variant requires an attacker to alter stored on-chain data after the preview.
In a controlled test, the authors sent an account's balance to a contract that returned as little as 1 wei, the smallest unit of ETH. They reported that several tested previews displayed a positive estimate and most did not clearly show the full outgoing amount.
The paper does not identify the wallet versions, settings, or simulation backends used by the historical victims. MetaMask's current documentation calls estimated balance changes predictions and warns that the final outcome is not guaranteed.
A Jan. 8, 2025 Etherscan transaction cited by the study records a Claim() call moving about 143.45 ETH through a contract Etherscan labels as phishing. The on-chain record supports the transfer described in the paper, although it cannot show what appeared in the user's wallet preview.
The authors recommend re-running simulations when relevant contract state or gas fields change. They suggest using the gas limit and gas price in the actual request, and testing current and future block-number and timestamp inputs. Their UI findings support showing the gross amount leaving a wallet alongside an accurate net balance change, so a negligible refund cannot be mistaken for a profit.
The preprint describes historical activity, not a live July or August attack wave. Its detector evaluation covered 44 contracts, including 30 generated with Gemini, and the linked code-and-data repository returned HTTP 401 when checked.
The aggregate results remain the authors' findings rather than an independently reproduced measurement.
Drafted by a large language model from the source reporting linked above, then screened by automated publishing checks. It is not read by a journalist before publication. Some articles cite our Alpha Score. Verify prices and figures against the original source. Educational coverage, not personalized advice.