DNS/CDN/frontend hash drift
Axelar Network'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: axelar.network, satellite.axelar.network (now squidrouter.com), and axelarscan.io are high-value brand surfaces. External hash-drift monitor not wired. No frontend incident or DNS hijack confirmed via public sources as of 2026-05-17. Note: satellite.axelar.network redirects to squidrouter.com (Squid Router, a separate entity) — change-management allowlist must track this migration. Baseline hash for JS bundle monitoring needs to be established.
Sources #
- URLSquid Router — Bridge, Swap & Build Across 100+ ChainsSquid Router (formerly satellite.axelar.network) — current redirect confirmedretrieved 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 →