DNS/CDN/frontend hash drift
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-105 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
T-09 phase-2 signal. Applicable — sushi.com is the primary user frontend. MISO 2021 supply-chain attack (contractor injected malicious JS into launchpad frontend) establishes that frontend compromise is a real, historically-realized attack vector for this protocol. GoPlus security integration added 2024 for transaction-level threat detection, but front-end hash monitoring (DNS/CDN/JS-bundle hash drift vs baseline) is not currently deployed. Production baseline hash for sushi.com not established. Cannot assess current posture without production monitoring.
Sources #
- URLJayPegs Automart — rekt.news (MISO supply-chain)MISO 2021 supply-chain attack — contractor JS injection into Sushi frontendretrieved 2026-05-17
Methodology #
Detect whether the hash of production frontend JS changes versus the prior published hash, or a DNS config change is detected.
See the full factor methodology and distribution across all protocols →