Reproduced Exploit

Superfluid Locker — Pumponomics can be skipped via `provideLiquidity`

1. Owner pre-sends WETH into the locker (not via provideLiquidity). 2. Calls provideLiquidity{value: dust}(supAmount). 3. Only dust * 1% is pumped (buy SUP); the position uses all WETH. 4. Full-sized LP with negligible pumponomics.

Jun 2025Otheruntagged2 min read

Chain

Other

Category

untagged

Date

Jun 2025

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: 58282-h-2-pumponomics-can-be-skipped-when-using-fluidlockerprovide. Standalone Foundry PoC and full write-up: 58282-h-2-pumponomics-can-be-skipped-when-using-fluidlockerprovide_exp in the evm-hack-registry mirror.


Vulnerability classes: access-roles · fee-theft · single-tx · known-pattern

Reproduction: self-contained Foundry PoC with only forge-std — no fork. output.txt · test/58282-…sol.

AuditVault taxonomy: lang/solidity · sector/dex · sector/streaming · platform/sherlock · severity/high · genome: access-roles · loss-of-funds/fee-theft · single-tx


Key info#

ImpactHIGH — structural buy-pressure (pumponomics) bypassed; protocol loses swap/LP fee intent
ProtocolSuperfluid Locker System — FluidLocker.provideLiquidity / _pump
Vulnerable codePumps only msg.value * 1% but LPs WETH.balanceOf(locker)
Bug classMismatch between pump base and LP inventory
FindingSherlock 2025-06-superfluid-locker-system · H-2 · #58282 · newspacexyz et al.
Reportjudging issue #210
SourceAuditVault
Fixsuperfluid-finance/fluid#27
Compiler^0.8.24 (PoC)
Reposherlock-audit/2025-06-superfluid-locker-system@d8beaeed

TL;DR#

  1. Owner pre-sends WETH into the locker (not via provideLiquidity).
  2. Calls provideLiquidity{value: dust}(supAmount).
  3. Only dust * 1% is pumped (buy SUP); the position uses all WETH.
  4. Full-sized LP with negligible pumponomics.

Vulnerable code#

SOLIDITY
_pump(weth, ethAmount * BP_PUMP_RATIO / BP_DENOMINATOR); // @> VULN: ethAmount = msg.value only
uint256 ethLPAmount = IERC20(weth).balanceOf(address(this)); // full inventory
_createPosition(ethLPAmount, supAmount);

Root cause#

Pump sizing keys off msg.value; LP sizing keys off balance. Pre-funded WETH is LPd without being pumped.

Preconditions#

  • Locker owner can transfer WETH in and call provideLiquidity.
  • Locker holds FLUID for the SUP side of the position.

Attack walkthrough#

  1. Deposit 1 ETH as WETH into the locker.
  2. provideLiquidity{value: 100 wei}(100e18 SUP).
  3. ethPumped == 1 (1% of 100); position holds ~1 ETH of WETH.

Diagrams#

sequenceDiagram participant Owner participant Locker as FluidLocker participant Pump as SwapRouter participant NPM as PositionManager Owner->>Locker: transfer WETH 1 ether Owner->>Locker: provideLiquidity value 100 wei Locker->>Pump: pump 1 wei only Locker->>NPM: mint with ~1 ether WETH Note over Locker: full LP dust pump

Impact#

Weakens Superfluid's intended buy-pressure; large LP positions can be opened while protocol fee/swap flow from pumponomics is nearly zero.

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.