bikini/exploitarium

A single archive of public exploit PoCs and vulnerability research writeups. At the time I post these, none have been reported. Feel free to report them...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 33 minutes ago
Added to GitGenius on September 4th, 2026
Created on June 23rd, 2026
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 1,277
Total Stargazers: 4,901 (+8)
Total Subscribers: 116 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.8 hours
Mean response time: 14.9 hours
90th percentile: 2.9 days
Tracked items: 8

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 54 days
Stale 30+ days: 1
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

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Exploitarium is a repository archive that collects public exploit proof-of-concepts and vulnerability research writeups.

The repository addresses the problem of scattered vulnerability research by consolidating multiple proof-of-concept exploits and their accompanying documentation in a single location. The approach preserves former standalone repositories as individual folders while adding new research entries as self-contained directories, each with its own README and tracked files. The maintainer notes that exploits are published after discovery but before public disclosure, and explicitly requests responsible handling of the material.

The repository is suited for security researchers, vulnerability analysts, and those learning exploit development. It serves as both a reference collection and an educational resource. The maintainer states the primary motivation is to attract people into the security field through accessible examples of vulnerability research and exploitation techniques.

The project's development reflects a deliberate methodology combining human expertise with automation. The maintainer has formal training in fuzzing and has published research on fuzzing methodology, using automated fuzzing workflows to identify vulnerabilities while hand-coding the actual proof-of-concepts themselves. Documentation was generated with AI assistance but reviewed for accuracy. The maintainer acknowledges that some exploits required language-specific assistance and credits external researchers where others discovered vulnerabilities independently. The stated intention to broaden proof-of-concepts for researchers unable to adapt them to their environments indicates ongoing refinement based on user feedback.