sunweb3sec/defihacklabs

Reproduce DeFi hacked incidents using Foundry.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 21 minutes ago
Added to GitGenius on September 9th, 2026
Created on June 10th, 2022
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 1,478
Total Stargazers: 6,782 (+0)
Total Subscribers: 136 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 days
Mean response time: 33.7 days
90th percentile: 183.0 days
Tracked items: 17

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 57 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (6)
  • PoC (1)

Most active issues this week

Detailed Description

DeFi Hacks Reproduce is a Foundry-based educational resource that recreates past decentralized finance security incidents as reproducible test cases.

The project addresses the need for hands-on learning about DeFi vulnerabilities by providing working proof-of-concept implementations of real hacking incidents. Each incident is reproduced using Foundry, Ethereum's testing framework, allowing developers to examine the exact mechanics of how attacks succeeded. This approach lets security researchers and developers study attack vectors in a controlled environment, understand root causes, and learn defensive patterns without requiring access to live networks or complex setup procedures.

Developers should use this resource for security education and incident analysis rather than as a reference for conducting attacks. The project suits teams building DeFi protocols who want to understand common vulnerability patterns, security auditors preparing for assessments, and blockchain developers strengthening their security knowledge. The repository includes transaction debugging tools and an Ethereum signature database alongside the incident reproductions, providing supplementary resources for investigation and analysis.

The project maintains an active collection of reproducible incidents with supporting documentation including root cause analysis. Development activity shows consistent expansion of the incident library and ongoing maintenance of test cases and supporting materials. The project provides structured contribution guidelines for community participation in adding new incident reproductions. Educational content is published alongside the code repository to help developers understand the technical details of each incident.