Avg attacker reconnaissance time for peer-class protocols
Liquid Collective (LsETH)'s assessment for RD-F-163 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Reconnaissance time for peer-class LST protocols (class-level signal): USPD reconnaissance pattern suggests 14-78 days of pre-strike activity for comparable DeFi protocols. No attacker-class reconnaissance signals currently active for Liquid Collective. January 2024 exit-daemon incident was internal/operational (software bug severity 0), not attacker-driven. The Allowlist access control creates friction against standard reconnaissance patterns (wallet interactions with protocol for information gathering are gated). No prior exploit history provides no protocol-specific reconnaissance baseline. Posture: no reconnaissance activity detected.
Sources #
- URLIncident Update Jan 30 - Liquid Collective DiligenceJanuary 2024 incident determined to be internal software bugs (exit daemon), not an attacker reconnaissance or strike pattern; no ETH at riskretrieved 2026-05-17
- Liquid Collective data cache - rekt incidents00-data-cache.json sources.rekt.incidents = []; no prior exploit confirming no past recon-to-strike patternretrieved 2026-05-17
Methodology #
Report the average number of days of attacker reconnaissance activity before a strike on peer-class protocols (lending/DEX/bridge/perps), sourced from the hack database.
See the full factor methodology and distribution across all protocols →