Prior exploit count
Fluid's assessment for RD-F-077 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
1 adverse incident: March 2025 Resolv/USR contagion event. Root cause was external (Resolv AWS key compromise → unbacked USR minting → wstUSR oracle mispricing at Fluid). Fluid absorbed ~$10–15M bad debt; $300M+ single-day TVL outflow. All bad debt repaid by team via short-term loan (final repayment announced March 2026). Zero protocol-level exploits of Fluid's own smart contract code. Score yellow (not green because a real loss event occurred; not red because root cause is external and fully remediated).
Sources #
- InternalFluid Data Cache — rekt.incidents emptyHacksdatabase grep returned 0 Fluid/Instadapp-specific hack files; data cache rekt.incidents: []retrieved 2026-04-29
- The Defiant — Resolv USR Exploit Fluid ImpactThe Defiant: DeFi Has Seen Resolv's $25M USR Exploit Many Times Before — Fluid absorbed >$10M bad debt, $300M+ outflowretrieved 2026-04-29
- Resolv USR Exploit Full Analysisresolv-usr-exploit.vercel.app: Fluid estimated bad debt $15–25M, 98% of wstUSR supply locked in Fluid at 6x leverageretrieved 2026-04-29
- Weex — Fluid Bad Debt Coverage AnnouncementWeex: Fluid 100% bad debts covered by short-term loan commitment by Lomashuk, cyberfund, weremeow, Fluid core teamretrieved 2026-04-29
Methodology #
Count the number of distinct incidents in the hack database affecting this protocol.
See the full factor methodology and distribution across all protocols →