Impermax V3 Hack

TOTAL LOST $300K
Low Flashloan Exploit / Other base

Summarize with AI

Affected Chain base Incident surface
Recovered - No recovery reported
All-Time Rank #1143 By amount stolen
Auditors 2 Prior security audits

Incident Overview

On April 27–28, 2025, Impermax V3 suffered an exploit resulting in a loss of approximately $300K, with an additional $300K–$350K at risk if borrowers repay loans and unlock vulnerable liquidity.

The attacker exploited a misvaluation in how Impermax handled uncollected trading fees used as collateral. By manipulating a low-liquidity Uniswap V3 pool and inflating the uncollected fee value through multiple swaps, they were able to borrow against this artificially high collateral. They then auto-compounded the fees at an incorrect price tick, reducing real collateral value due to impermanent loss, before reverting the tick to extract value.

The attacker repeated this process to drain available liquidity and dilute lenders via the restructureBadDebt() function, securing stolen funds before legitimate users could react.

Incident Report

Protocol / Project Impermax V3
Date of Incident
Affected Chain(s) base
Attack Technique Flashloan Exploit / Other
Classification Protocol Logic / Yield Aggregator
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Smart Contract Language Solidity
Official Website www.impermax.finance/
Protocol Twitter/X @impermaxfinance
Team Anonymous
Source Code Unverified

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of flashloan exploit / other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with base smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Impermax V3's contract logic - root cause: protocol logic / yield aggregator
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Flashloan Exploit / Other audit checklist and test coverage
Audited by Audit Report 1, Audit Report 2 — still lost $300K. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Impermax V3, these are the critical security checks that could have prevented this incident (April 2025).

  • Verify all logic paths related to Flashloan Exploit / Other are guarded by proper access controls and input validation - see the Flash Loans Attacks attack class for patterns
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Security Audit History

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Flash Loans Attacks examples →

Sources & References

Learn to Prevent the Next Impermax V3

The Impermax V3 hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial