Avg attacker reconnaissance time for peer-class protocols
Meteora's assessment for RD-F-163 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Cat 11 analytical factor. No Meteora-specific external-attacker reconnaissance time datum exists (no contract exploit precedent). For Solana DEX class analogues: Raydium Dec 2022 hack was opportunistic/rapid once private key was compromised (single-session, no extended reconnaissance). Drift Protocol Apr 2026 DPRK attack involved 6 months of social engineering buildup (insider implant class, not DEX reconnaissance). The LIBRA/M3M3 matter was alleged insider manipulation over months of coordination (Oct 2024 M3M3, Feb 2025 LIBRA), not external reconnaissance. DEX protocols with permissionless access (like Meteora DBC) have low reconnaissance barriers — anyone can interact without prior relationship. No Meteora-specific attacker reconnaissance time datum is available for scoring. Curator must establish protocol-class baseline from hack DB.
Sources #
- URLMeteora on Solana: Project Review, Programs, Token, MetricsRaydium 06-realtime-intel.md precedent: Dec 2022 attack was rapid/opportunistic (no extended reconnaissance); Drift 2026 DPRK involved 6-month buildup (insider implant class). Meteora has no contract exploit precedent for this factor.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 →