Reproduced Exploit
OmoVault — topOff only accepts agent id 0, so users cannot redeem
Dynamic accounts store agents under an id. topOff requires agents(0) == msg.sender. Id 0 is never registered, so the agent stored at id 1 cannot redeem. 1000 AST deposited in the vault stays there. A vault that checks the id the caller passes pays that 1000 to the same agent.
Chain
Other
Category
access-control
Date
Jan 2025
Source
AuditVault
EVM Playground
Source-level debugger — step opcodes and Solidity in sync
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.
Source & credit. Reproduction of a public audit finding curated by AuditVault — the original finding: 53316-c-05-the-users-are-not-able-to-redeem-their-funds-pashov-aud. Standalone Foundry PoC and full write-up: 53316-c-05-the-users-are-not-able-to-redeem-their-funds-pashov-aud_exp in the
evm-hack-registrymirror.
Vulnerability classes: vuln/access-control/broken-logic · vuln/dos/frozen-funds
Key info#
| Protocol | OmoVault |
| Finding | Pashov Audit Group C-05, AuditVault 53316 |
| Vulnerable code | OmoVault.topOff checks agents(0) |
| Harm | Redeem reverts and 1000 AST stays in the vault. Agent id 1 pays 1000 on the control vault. |
| Chain | local synthetic |
TL;DR#
Dynamic accounts store agents under an id. topOff requires agents(0) == msg.sender. Id 0 is never registered, so the agent stored at id 1 cannot redeem. 1000 AST deposited in the vault stays there. A vault that checks the id the caller passes pays that 1000 to the same agent.
The vulnerable code#
OmoAgent agent = OmoAgent(payable(userAccount));
// @> VULN: only agent id 0 is checked, and that id was never registered
require(agent.agents(0) == msg.sender, "UNAUTHORIZED_AGENT");
The finding's recommendation is to pass the agent id instead of the constant 0.
Root cause#
The authorization read is hardcoded to slot 0 of the agent mapping. Registration uses a non-zero id. No caller can satisfy the check, so the transfer under it never runs.
Preconditions#
The account has an agent at id 1 and nothing at id 0. The vault holds the user's assets. The caller is that registered agent.
Attack walkthrough#
agents(0)is the zero address.agents(1)is the caller.- 1000 AST is transferred into the vault.
topOffrevertsUNAUTHORIZED_AGENT. The vault balance is still 1000.- The control vault is called with id 1 and transfers 1000 AST to the agent.
Diagrams#
Impact#
Users cannot redeem through topOff. The 1000 AST in the vulnerable vault remains after the registered agent calls it. The same agent, checked at id 1, is paid 1000 from the control vault.
Remediation#
Pass the account's agent id into the check: require(agent.agents(agentId) == msg.sender).
How to reproduce#
cd 53316-c-05-the-users-are-not-able-to-redeem-their-funds-pashov-aud_exp
forge test -vv
Sources#
- AuditVault finding: https://github.com/Auditware/AuditVault/blob/main/findings/53316-c-05-the-users-are-not-able-to-redeem-their-funds-pashov-aud.md
- Pashov report: https://github.com/pashov/audits/blob/master/team/md/Omo-security-review_2025-01-25.md
Sources & further analysis#
Reproductions & code
- Standalone PoC + full trace: 53316-c-05-the-users-are-not-able-to-redeem-their-funds-pashov-aud_exp (evm-hack-registry mirror).
- AuditVault finding: 53316-c-05-the-users-are-not-able-to-redeem-their-funds-pashov-aud.
Alerts & third-party analyses
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.