Reproduced Exploit

Mass — low-level call to an empty account falsely succeeds

The helper accepts delegatecall success from an account with no code. EVM semantics return true for an empty destination, so the caller observes success without executing the requested payload.

Feb 2023Otherdependency3 min read

Chain

Other

Category

dependency

Date

Feb 2023

Source

AuditVault

EVM Playground

Source-level debugger — step opcodes and Solidity in sync

evm-hack-analyzer

The attack is replayed in an in-browser EVM preloaded with the exact dumped fork state. The execution tree shows every call; step by Solidity line or by opcode across all depths — source, Stack, Memory, Storage, Balances (native / ERC-20 / NFT), Transient storage and Return value stay in sync. Click a tree node, opcode, or source line to jump. No backend, no live RPC.

Loading fork state…

Source & credit. Reproduction of a public audit finding curated by AuditVault — the original finding: 29664-lack-of-contract-existence-checks-on-low-level-calls-trailof. Standalone Foundry PoC and full write-up: 29664-low-level-call-missing-existence-check_exp in the evm-hack-registry mirror.


Vulnerability classes: vuln/dependency/unsafe-external-call · vuln/input-validation/missing · vuln/logic/wrong-condition

Reproduction: Fully local synthetic; run forge test and inspect output.txt. The Playground bundle replays the same 29664-low-level-call-missing-existence-check invariant.

Key info#

FieldValue
LossA wallet can record successful execution while no implementation code ran
Vulnerable contractCallHelper / Proxy (reconstructed)
Attacker EOA0x1111111111111111111111111111111111111111 (synthetic caller)
Attack contractExploit
Attack txLocal Exploit.run() call (no historical transaction)
Chain · block · dateEthereum · local stub 0x1181d03 · 2023-02
CompilerSolidity 0.8.35 (pragma ^0.8.24)
Bug classvuln/dependency/unsafe-external-call · vuln/input-validation/missing · vuln/logic/wrong-condition

TL;DR#

The helper accepts delegatecall success from an account with no code. EVM semantics return true for an empty destination, so the caller observes success without executing the requested payload.

Background#

AuditVault finding 29664-low-level-call-missing-existence-check is an audit-time issue rather than a historical exploit. This write-up reduces the report to one state transition and keeps the claimed harm assertion executable offline.

The vulnerable code#

The minimized source is explicitly marked RECONSTRUCTED and preserves the report's blamed operation with an @> VULN marker in test/29664-low-level-call-missing-existence-check.sol. It is byte-identical to the Playground synthetic source. No verified production source was available in this local checkout.

Root cause#

functionDelegateCallUnverified omits an extcodesize/code.length check before accepting success.

Preconditions#

The affected protocol path is deployed; the attacker can reach the public operation described in the report. The synthetic removes unrelated integrations while preserving the state and authorization assumptions required for the finding.

Attack walkthrough#

  1. delegatecall to 0xBEEF returns true, while code.length remains zero and no state change occurs.
  2. The run() method requires the broken invariant and sets confirmed; the Forge trace records a passing test at output.txt:355.
  3. The remediation is to validate the accounting/state transition before accepting the external call or to consume the one-time state.

Diagrams#

flowchart TD A["Attacker invokes public path"] --> B["Vulnerable state transition"] B --> C["Inconsistent accounting or revert"] C --> D["Reported protocol harm"]

Remediation#

Validate external addresses and returned balances before updating state, and make each one-time transition explicit. Add invariant tests covering zero/deflationary/epoch-boundary inputs.

How to reproduce#

BASH
cd 29664-low-level-call-missing-existence-check_exp
forge test -vvv

The browser replay uses scripts/poc-configs/29664-low-level-call-missing-existence-check.mjs and the same local-deploy Exploit contract.

Sources#


Sources & further analysis#

Reproductions & code

Alerts & third-party analyses

  • Web3Sec X hacked database: search.
  • Rekt leaderboard: search.
  • Solodit incident search: search.

These dashboards index community alerts tweets, post-mortems, and independent write-ups. Reach them through the protocol name above to cross-check this reproduction against other analyses.