Prior exploit count
Raydium'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 confirmed incident: December 16, 2022 admin-key compromise via trojan, ~$4.4M loss. Attacker-side recovery: zero (funds sent to Tornado Cash). LP-side: Raydium compensated 90–100% of principal + 20% bonus RAY from team vesting allocation (2,737,521.92 RAY distributed). Strict taxonomy score red (any unrecovered loss); scored yellow reflecting that user-side was fully compensated and only 1 incident exists. No further incidents through 2026-04-29.
Sources #
- GitHubRaydium Hack Report (proprietary hacksdatabase)hacksdatabase/hacks/raydium-rekt.md — Raydium hack reportretrieved 2026-04-29
- Raydium removed the /updates/archive/ section in the 2024-2025 docs reorganization; the transparency-on-exploit-compensation-funds page is gone with no canonical replacement on docs.raydium.io. The Dec 2022 exploit compensation plan (RAY buyback treasury + vested team allocation; LPs in RAY-pairs claimed 100%, non-RAY pairs claimed 90% + 10% in RAY + 20% bonus) is documented in third-party reporting (Cointelegraph 'Raydium announces details of hack, proposes compensation for victims', CertiK 'Raydium Protocol Exploit Incident Analysis'). archive.org is blocked from this environment so a snapshot URL could not be captured. Grader to substitute a third-party citation if direct primary source needed. [dead-link, original: https://docs.raydium.io/raydium/updates/archive/transparency-on-exploit-compensation-funds]retrieved 2026-05-06
- Raydium — Detailed Post-Mortem and Next StepsRaydium detailed post-mortem Medium post (2022-12-17)retrieved 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 →