Peapods Finance Hack

TOTAL LOST $4K
Low Other

Summarize with AI

Affected Chain 2025 Incident surface
Recovered - No recovery reported
All-Time Rank #1993 By amount stolen
Auditors 1 Prior security audit

Incident Overview

On February 8, 2025, Peapods Finance suffered an exploit due to a vulnerability in its reward contract’s depositFromPairedLpToken function. The attacker manipulated the _slippageOverride parameter, executing a sandwich attack that drained funds from the contract. The total loss amounted to approximately $3,500.

The exploit stemmed from the contract’s lack of validation on the _slippageOverride parameter, which directly influenced the amountOutMinimum value in token swaps. The attacker first manipulated the token price by executing a large trade before calling depositFromPairedLpToken with an extreme _slippageOverride value of 999. This forced the contract to accept unfavorable trade conditions, allowing the attacker to back-run their transaction and sell tokens at an inflated price for profit.

Peapods Finance has acknowledged the exploit and is currently investigating the incident.

Incident Report

Protocol / Project Peapods Finance
Date of Incident
Attack Technique Other
Classification Yield Aggregator
Primary Source View Post-Mortem #1

Protocol Information

Protocol Type Yield
Official Website peapods.finance/app
Protocol Twitter/X @PeapodsFinance
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 other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Peapods Finance's contract logic - root cause: 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 Other audit checklist and test coverage
Audited by Audit Report 1 — still lost $4K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Other are guarded by proper access controls and input validation
  • 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

Sources & References

Learn to Prevent the Next Peapods Finance

The Peapods Finance 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