Research module F
Historical Security Incidents
Case studies of past security incidents at tokenized real-world assets, researched from public forensic reporting, issuer statements and independent coverage, and reviewed before publication. Historical and read-only: not live monitoring, not part of the onchain event scans, and not an investment assessment.
- Published case studies
- 0
- Each reviewed by two researchers
- Networks covered
- 0
- None yet
- Held for review
- 1
- Counted, not shown
Scope
What a case study is, and is not
Historical cases are their own dataset. They sit beside the onchain security events and the index, and are never merged into either.
A case study is
- A reviewed account of one past incident at a tokenized real-world asset, built from public forensic reporting, issuer statements and independent coverage.
- Every factual statement is a claim with its basis — observed onchain, an issuer statement, a researcher's inference, or independent reporting — and the sources it rests on. Analysis is labelled as such and names the claims it draws on.
- Figures are kept apart by kind. Token quantities, notional value at a reference price, attacker proceeds, confirmed losses and holder compensation are never summed or substituted for one another.
- Open questions are published with the case, including what the sources do not establish.
A case study is not
- Not live monitoring. A case study is historical research, dated by its review, and nothing here updates between releases.
- Not part of Security Events. Case studies are not decoded onchain events, are not counted in that module's figures, and say nothing about which contracts its scans have covered.
- Not a Decoda classification by default. A publicly reported incident stays publicly reported unless two researchers confirm it on independent sources.
- Not part of the Security Controls Index. A case changes no score, state or position, and an asset outside the index is not added to it.
- Not an investment assessment, and not a finding about any asset's current security.
Data table
Case studies, oldest first
Search and filter every case this build publishes. Each links to its full case study and to the evidence it rests on.
Showing 0 of 0 case studies
No case study has been published yet
Case studies are published only after their claims are checked against their sources and two researchers approve them. Held cases are counted above, not listed.
By category
Incidents by security-control category
Counts of case studies, not rates. The cases are those researched so far, not a sample of all incidents, so no share or average is drawn from them. The control category is the index category of the first control a case bears on.
No case study is published yet, so there is nothing to count. 1 case study is held for review and counted only in the figures above.
Review
How a case study is published and classified
Publication and classification are both derived from recorded reviews. Neither can be set by hand, and a case that does not meet the bar stays held.
Publication
- Review pending
- Held from the published site and downloads until its claims are checked and two researchers approve it.
- Published
- Every claim checked against its sources, every source retrieved, and the current content approved by two researchers.
The bar: every claim confirmed against each source it cites by a named researcher; every cited source retrieved, under the title it is published with, on at least two independent hosts; no unread leads; and current approval of the case's exact content by 2 different researchers. Editing the case after approval leaves the approvals behind.
Classification
- Publicly reported
- Reported in public sources. Not classified as a confirmed incident by Decoda.
- Confirmed incident
- Confirmed by two Decoda researchers on sources spanning independent hosts, at least one of them not a block explorer.
The same bar a decoded event must clear to be a confirmed incident, applied separately here: a case study is never read as a classification of any onchain event, and a classification here never changes one there.
Open data
Downloads
Generated at build time from the case files, holding exactly the case studies this page lists.
- Historical incidents dataset JSONEvery published case study as recorded — claims, sources, timeline, figures, lessons and open questions — with its review status.
- Incident claims CSVOne row per claim: case, basis, source-check status, statement and the sources it cites.
Important context
Scores measure publicly observable technical controls and documentation at the stated snapshot date. They are not smart-contract audits, credit ratings, investment recommendations, or assessments of an organization's complete security posture.