ProtoCrash
Coverage-Guided Protocol Fuzzer for Vulnerability Discovery
ProtoCrash is a smart mutation-based fuzzer designed to find crashes and vulnerabilities in network protocol implementations. Built with intelligent feedback-driven fuzzing techniques, it targets custom protocols, binary formats, and network services.
Features
- Coverage-Guided Fuzzing - AFL-style instrumentation for intelligent test case generation
- Distributed Fuzzing - Multi-process parallelization for maximum throughput
- Multi-Protocol Support - HTTP, DNS, SMTP, custom binary protocols
- Smart Mutation Engine - Context-aware mutations based on protocol structure
- Crash Detection - Automatic crash analysis, classification, and exploitability assessment
- Real-Time Dashboard - Live fuzzing statistics with keyboard controls
- Report Generation - Text, JSON, and HTML reports with visualizations
- Minimal Dependencies - Pure Python implementation
- Extensible - Easy to add custom protocol parsers and mutation strategies
Installation
pip install protocrash
Or install from source:
git clone https://github.com/noobforanonymous/ProtoCrash.git
cd ProtoCrash
pip install -e .
CLI Usage
Fuzzing Commands
# Basic fuzzing with real-time dashboard
protocrash fuzz --target ./vulnerable_app --corpus ./seeds --crashes ./crashes
# Distributed fuzzing with 8 workers
protocrash fuzz --target ./vulnerable_app --workers 8 --duration 3600
# Protocol-specific fuzzing
protocrash fuzz --target tcp://localhost:8080 --protocol http --timeout 5000
Crash Analysis
# Analyze crashes with exploitability assessment
protocrash analyze --crash-dir ./crashes
# Classify and deduplicate crashes
protocrash analyze --crash-dir ./crashes --dedupe --classify
# Filter by crash type
protocrash analyze --crash-dir ./crashes --type segv
Report Generation
# Generate text report
protocrash report --campaign-dir ./campaign --format text
# Generate HTML report with charts
protocrash report --campaign-dir ./campaign --format html --output report.html
# Generate JSON report for automation
protocrash report --campaign-dir ./campaign --format json --output report.json
Dashboard Controls
When running the real-time dashboard:
p- Pause/resume fuzzingr- Refresh displayq- Quit gracefully
Distributed Fuzzing
ProtoCrash supports multi-process distributed fuzzing for increased throughput.
Python API
from protocrash.distributed import DistributedCoordinator
from protocrash.fuzzing_engine.coordinator import FuzzingConfig
config = FuzzingConfig(
target_cmd=["./target", "@@"],
corpus_dir="./corpus",
crashes_dir="./crashes",
timeout_ms=5000
)
# Launch distributed fuzzing with 8 workers
coordinator = DistributedCoordinator(config, num_workers=8)
coordinator.run(duration=3600) # Run for 1 hour
Architecture
- Master-Worker Model: One coordinator process manages N worker processes
- Corpus Synchronization: Workers share interesting test cases via filesystem
- Statistics Aggregation: Real-time performance metrics from all workers
- Crash Deduplication: Unique crash detection across all workers
Performance
Distributed fuzzing scales efficiently:
- 1 worker: ~50,000 exec/sec
- 4 workers: ~180,000 exec/sec
- 8 workers: ~350,000 exec/sec
- Scaling efficiency: ~87.5%
Project Status
| Metric | Value |
|---|---|
| Tests | 859 passing (100%) |
| Coverage | 96% |
| Production Code | 9,093 lines |
| Test Code | 12,661 lines |
| Platforms | Linux (full), Windows (partial) |
Documentation
- Usage Guide
- Setup Instructions
- System Architecture
- Fuzzing Engine Details
- Distributed Fuzzing Guide
- CLI & Reporting
How It Works
Input Corpus → Smart Mutation → Target Execution → Coverage Feedback → Crash Detection
↑ ↓
└──────────────── New Interesting Cases ──────────────┘
ProtoCrash uses coverage-guided fuzzing to intelligently generate test cases that explore new code paths in the target application. It monitors the target for crashes, hangs, and memory corruption, automatically saving reproducible test cases.
Requirements
- Python 3.11+
- Linux (recommended for best coverage support)
- Target application for fuzzing
Ethical Use
ProtoCrash is designed exclusively for authorized security testing, vulnerability research, and software quality assurance. Only use this tool on systems you own or have explicit permission to test.
See Ethical Guidelines for detailed usage policy.
Author
Regaan
- GitHub: @noobforanonymous
License
MIT License - see LICENSE file for details
Acknowledgments
Built with inspiration from AFL, LibFuzzer, and Boofuzz. Designed for the security research community.
Metadata
Release files for protocrash 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| protocrash-1.0.0.tar.gz | 86.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| protocrash-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 181.1 kB
Release files / protocrash-1.0.0.tar.gz
| Download URL | protocrash-1.0.0.tar.gz |
|---|---|
| Size | 86.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a004f07562be9ff11740cdec578ddfcc69e4983918da84d288ecb519ef91678b
|
|
BLAKE2b-256 checksum How to use checksums |
1651ce94c1895078f1b4632476bc916e82302f888a65ec4dd522b5e3b402da02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 30, 2025.
Transparency logRelease files / protocrash-1.0.0-py3-none-any.whl
| Download URL | protocrash-1.0.0-py3-none-any.whl |
|---|---|
| Size | 94.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a2fa872d35fb8e0315dbdc288b8e8daecef3991255c5d217dcdc18cd4dc7186
|
|
BLAKE2b-256 checksum How to use checksums |
d224e3dd14cf242fcde61a54151bce83ed7a27e3012ab2ee12341a40763f9938
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 30, 2025.
Transparency logSecurity for protocrash 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for protocrash-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 30, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.