Deployer address prior on-chain history
Raydium's assessment for RD-F-114 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Original admin EOA (HggGrUeg4ReGvpPMLJMFKV69NTXL1r4wQ9Pk9Ljutwyv) was a team-controlled key with normal-dev-history — no prior rug deployments linked. This key was compromised by trojan malware in December 2022 (not insider misconduct). Post-December 2022, upgrade authority transferred to Squads V4 3/4 multisig. Current authority is the Squads multisig, not an EOA. Historical EOA is categorized as normal-dev-history with the caveat of the compromise incident.
Sources #
- URLRaydium Protocol Exploit Incident Analysis | CertiKCertiK exploit analysis — compromised EOA identifiedretrieved 2026-04-29
- Detailed Post-Mortem and Next Steps | Raydium | MediumRaydium December 2022 post-mortem — EOA compromise detailsretrieved 2026-04-29
Methodology #
Classify the deployer address history as: none (fresh address) / normal-dev-history (prior protocol deploys, non-flagged activity) / linked-to-prior-rug (deployer used in prior known rug).
See the full factor methodology and distribution across all protocols →