Incident response time (minutes)
Yearn Finance's assessment for RD-F-085 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Most-recent incident (#4, 2023-12-16): External researcher William Li spotted the attack in real-time ('Another Yearn V1 vault attack is underway!'); PeckShield flagged simultaneously; Yearn's own response was characterization of the vault as 'deployed over 2,100 days ago' — no war room, no on-chain action possible (immutable contract). Official team statement timing not precisely documented but likely within hours via social media. Incident #1 (2021-02-04): 11 minutes to vault disable (green-class response). Incident #3 (2023-11-30): War room ~20 minutes post-exploit. Scoring on most-recent incident #4 where team statement timing is indeterminate but external detection was real-time; no formal ≤60 min team statement confirmed.
Sources #
- URLYearn Security Disclosure 2021-02-04Yearn Security 2021-02-04 disclosure — 21:45 detection, 21:56 vault disabled = 11 min responseretrieved 2026-05-16
- Yearn Finance 4th Exploit — response timelinehacksdatabase/hacks/yearn-rekt4.md — William Li external detection, real-time; Yearn response characterizationretrieved 2026-05-16
Methodology #
Measure the time in minutes from the first exploit transaction to the first official team statement for the most recent incident.
See the full factor methodology and distribution across all protocols →