Security-Council threshold reduction (RT)
Aerodrome Finance's assessment for RD-F-182 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
6B exploit-in-progress (F182 batch-24): Security-Council threshold reduction (RT). Emergency Council multisig 0x99249b10593fCa1Ae9DAE6D4819F1A6dae5C013D and team multisig 0xE6A41fE61E7a1996B59d508661e3f524d6A32075 exist. Signer counts and thresholds unknown (Safe API 403, data cache safe_multisigs: []). Baseline M/N cannot be established without this data. Emergency Council created 2025-10-08 (207 days ago) — this was a new multisig creation event, but it predates this assessment window and is not flagged in public reporting as suspicious. ChangedThreshold/AddedOwner/RemovedOwner event monitoring not configured for dry-run.
Sources #
- EtherscanAerodrome Emergency Council — BaseScanEmergency Council 0x99249b10593fCa1Ae9DAE6D4819F1A6dae5C013D — GnosisSafeProxy created 2025-10-08 (207 days ago per BaseScan). Threshold/signer count not accessible via BaseScan UI.retrieved 2026-05-04
Methodology #
Detect in real-time whether the bridge/protocol Security Council multisig executes a threshold reduction (e.g. 3/5 → 2/5), timelock removal, or new-signer addition within ≤14 days of either of those events.
See the full factor methodology and distribution across all protocols →