What happened, and when
A dated registry of exploits and protocol events for event-study work. Every entry names its source and links back. Nothing here is unattributed, and no amount is estimated by us.
185 events
| Date | Event | Chains | Loss | Returned | Source |
|---|---|---|---|---|---|
| 2026-04-28 |
YieldCore: $399 Thousand exploit
Access Control · Improper Access Control
Access Control · Improper Access Control · DeFi Protocol
|
Ethereum | $399 Thousand | — | DeFiLlama |
| 2026-04-28 |
JUDAO: $228 Thousand exploit
Token & Share Accounting · Arithmetic Error
Token & Share Accounting · Arithmetic Error · Token
|
BSC | $228 Thousand | — | DeFiLlama |
| 2026-04-28 |
Quant: $138 Thousand exploit
Access Control · Arbitrary External Call
Access Control · Arbitrary External Call · Token
|
Ethereum | $138 Thousand | — | DeFiLlama |
| 2026-04-27 |
ZetaChain: $334 Thousand exploit
Access Control · Token Approval Abuse
Access Control · Token Approval Abuse · bridge · Chain
|
Ethereum Base Polygon +3 | $334 Thousand | — | DeFiLlama |
| 2026-04-27 |
Singularity Finance: $413 Thousand exploit
Oracle Manipulation · Oracle Misconfiguration
Oracle Manipulation · Oracle Misconfiguration · DeFi Protocol
|
Base | $413 Thousand | — | DeFiLlama |
Exploit records come from the public DeFiLlama hacks registry and are re-imported as recovery figures are updated. Depegs are detected daily from the platform's own hourly bars, and governance upgrades are read from Governor Bravo logs on chain; each row names its source. Curated entries add the transactions and addresses behind an event so it can be traced in the explorer and lined up against price windows. We publish what the source publishes, and amounts we cannot attribute are shown as blank, never filled in. The CSV carries the same rows as the filter you are looking at, one event per line, up to 5,000; past that, request the registry as a data export.