Saturn Protocol exploit analysis
Saturn Protocol's `release` was paid from a treasury held in a token whose supply cap the attacker had inflated. DeFiHackLabs reconstructs the cap-inflate-and-release drain.
- Reported loss
- 0 (Disclosure only; no exploit occurred), per DeFiHackLabs
- Occurred
- Logged
- Source
- DeFiHackLabs
Logged as “2026-04-14: Vulnerability Disclosure on Saturn Protocol”.
Analysis1 min read
Saturn Protocol's treasury paid out via a release function whose target was a token whose supply-and-supply-cap accounting the attacker had previously moved. The attacker inflated the cap to free the release, walked the treasury's balance out.
DeFiHackLabs reconstructs the sequence against the live state; total loss is captured in the PoC.
What would have prevented it: a release path that pins the cap to the deploy-time value, or any release that requires a multi-block delay.
Other exploits
- AaveRebalancerCreditDelegation exploit analysis 19 Apr 2026
- XLootStaking exploit analysis 15 Apr 2026
- MONA LisaVault exploit analysis 14 Apr 2026
- SubQuerySettings exploit analysis 12 Apr 2026
- SquidMulticallAllowanceDrain exploit analysis 7 Apr 2026
- PerpPair exploit analysis 5 Apr 2026
Query every incident yourself — free, no signup
Updated 14 Oct 2026. Figures are as reported by the sources listed above and are not independently verified.
The crypto data layer for humans, apps, and AI agents.
