On March 2025, wKeyDAO suffered a other — the first of 188 documented other incidents in our archive where the loss figure was not publicly disclosed but the exploit pattern is documented below.
Attack Mechanics: How the wKeyDAO Other Played Out
Exploit Class Applied to wKeyDAO
The wKeyDAO incident on March 16, 2025 is classified as a Other. A specific exploit class outside the most common buckets. In the full archive, wKeyDAO is 1 of 188 documented other incidents.
wKeyDAO in Context
The wKeyDAO incident joins a class whose largest loss to date is MIMSpell (2024) at $65M.
Prior Other Before wKeyDAO
The nearest other incident before wKeyDAO was H2O, 2 days earlier on March 14, 2025 ($22.5K lost). The same exploit class surfaced again within the other attack surface.
wKeyDAO Vulnerability Signature
The primary source categorises the wKeyDAO exploit specifically as “unprotected function”. This narrower label is entity-specific: it reflects how the wKeyDAO contract failed, rather than the broad other pattern alone.
Impact & Recovery for wKeyDAO
wKeyDAO Loss Figure
The loss figure for wKeyDAO is not publicly disclosed. The primary source reports the exploit in non-USD terms, so no USD estimate is published here. For reference, the average loss across 188 other incidents in our archive is $2.03M.
Timeline Since the wKeyDAO Incident
The wKeyDAO exploit occurred 1.1 years ago (394 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for wKeyDAO
Public post-mortem / on-chain analysis for the wKeyDAO incident: view source.
FAQ
How much did wKeyDAO lose?
The wKeyDAO loss figure is not publicly disclosed. The primary source reports the exploit in non-USD token terms, so no USD estimate is published here.
When did the wKeyDAO hack happen?
The wKeyDAO exploit was recorded on March 16, 2025 — 394 days ago.
What type of exploit hit wKeyDAO?
The wKeyDAO incident is classified as a Other. A specific exploit class outside the most common buckets.
How common is the Other pattern seen at wKeyDAO?
Our archive contains 188 documented other incidents. The wKeyDAO incident is one of them.
How does wKeyDAO compare to the largest Other attack?
The largest other incident in our archive is MIMSpell (2024) at $65M. The wKeyDAO loss was not publicly disclosed.
What is the key feature of the proposed defense's post-processing module?
It flips the loss trend locally without altering the classifier's decision-making process.
What is the significance of using a GARCH model with exogenous regressors?
To incorporate the impact of COVID-19 as an external factor influencing volatility and returns.