Incident Overview
On July 8, 2025, Peapods Finance was exploited for ~$200k (~78 ETH) after an attacker used an exploit contract to drain assets from a vulnerable pod, with all stolen funds later routed through ChangeNow and FixedFloat.
The attacker, operating from 0x277da2d1…52a846, targeted a flaw in Peapods’ share-accounting logic that allowed them to artificially inflate redeemable pod shares via the exploit contract 0x7212de58…5ad006. This manipulation let them withdraw assets belonging to the victim wallet 0xd1538a9d…967257, effectively draining the pool in a single transaction. After extracting the funds, the attacker quickly laundered them through ChangeNow and FixedFloat, leaving the protocol illiquid and the affected pod insolvent.
Incident Report
Protocol Information
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to USPD, these are the critical security checks that could have prevented this incident (December 2025).
- Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control 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 TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next USPD
The USPD 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.