💥 Hacks Database
This is the official open archive of real-world smart contract hacks, curated and maintained by the LancerShield community.
Each entry provides:
- Structured metadata with attacker details, entry points, exploited vectors
- Transaction breakdown and timeline of the attack
- Financial loss and impact scope
- Links to on-chain evidence and verified disclosures
📂 Categories
Hacks are classified by severity using the LancerShield Severity Framework:
- Critical (C) – Complete fund drain, governance seizure, or protocol-wide failure
- High (H) – Major loss, access breach, or control bypass across multiple contracts
- Medium (M) – Exploit under edge conditions, partial losses or targeted manipulation
- Low (L) – Minor impact or contained incident with negligible damage
- Informational (I) – Attempted but failed exploits, or recon-level attacks
🧠Contributing
Want to submit a hack ?
- Use the template to format your submission
- Follow the contribution guide
- Submit via Pull Request — our reviewers will validate and merge after review
🚀 Future Use
This database will serve as:
- A canonical dataset for CVR exploit prediction
- Case studies for auditors, educators, and incident response teams
- A historical record to track the evolution of Web3 attack surfaces