v3 → v4
Scores
trust_score8 → 8
severity_base— → —
score_modifier-5.88 → -5.88
Sections
Exploit Overview
unchanged
Root Cause: Single-EOA Admin Control with No Governance Safeguards
unchanged
Attack Mechanics
unchanged
Institutional Background and Prior Funding
unchanged
Protocol Response and Incident Communication
unchanged
Broader Context: April 2026 DeFi Exploit Surge
unchanged
Security Audit and Governance Assessment
unchanged
Timeline events
No timeline changes.
Accepted submissions
- removedurlincriminating
{"url":"https://www.halborn.com/blog/post/explained-the-wasabi-protocol-hack-april-2026","kind":"url"}- removedurlincriminating
{"url":"https://www.theblock.co/post/399558/wasabi-protocol-hit-by-more-than-5-million-exploit-across-multiple-chains-security-firms-say","kind":"url"}- removedurlincriminating
{"url":"https://www.coindesk.com/tech/2026/04/30/wasabi-protocol-drained-for-usd4-5-million-in-apparent-admin-key-compromise","kind":"url"}Each version is bound to the decision event that created it. Verify the chain anchor for either via the audit log.
v3 hash: 766frps6xUBbDStSpGT38hpzwBT8fjPrG9AaraFwr4Ua
v4 hash: d4b06390b0ff47027ac885fb8ebc658573ded68f0087301afe6412f5953d5026