Avg attacker reconnaissance time for peer-class protocols
Spiko'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 #
No active reconnaissance activity identified targeting Spiko. USPD 78-day reconnaissance baseline from T-01: attacker-labeled wallets show 30-90 day reconnaissance windows before strike. RWA-class specific: Drift Apr 2026 involved 6-month reconnaissance. Spiko profile §10 confirms zero incidents in 23-month live history. No test-transaction patterns from known attacker addresses. Clean baseline — no current reconnaissance signal.
Sources #
- InternalT-09 / T-01 — reconnaissance baselineT-09 §4.10 / T-01 §3.K: USPD 78-day reconnaissance pattern; Drift 6-month social engineering. Spiko shows no analogous pre-strike pattern.retrieved 2026-05-16
- Spiko profile — clean incident record00-profile.md §10: No known incidents. 00-data-cache.json rekt.incidents: []. 23-month clean operational history.retrieved 2026-05-16
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 →