🎯 bounthunt — Bug Bounty Recon & Orchestration
Scope-aware recon orchestration for bug bounty programs.
🚀 Demo
$ bounthunt monitor scope.yaml
🔄 Starting monitoring loop...
[INFO] Checking scope.yaml...
[INFO] Scan completed. 12 new hosts discovered.
[INFO] 2 new endpoints found on example.com
[INFO] 1 new vulnerability found via nuclei
[SUCCESS] Sending notification to Telegram...
$ bounthunt report --format html
📊 Generating diff report...
✅ Report saved to reports/diff_2026_07_12.html
❓ Why bounthunt?
| Question | Manual approach | With bounthunt |
|---|---|---|
| What changed since last week? | diff two terminal buffers |
bounthunt monitor |
| Did I scan out of scope? | "Hope you checked" | Scope guard blocks it |
| Where is my scan data? | Scattered text files | SQLite with full history |
| Can I share findings? | Paste terminal output | Professional HTML/MD reports |
✨ Features
- Scope Guard — YAML allow/deny list prevents accidental out-of-scope scanning
- Diff Monitoring — Tracks new hosts, ports, findings, endpoints across scan runs
- SQLite Persistence — Every scan stored with timestamps, queryable and auditable
- Professional Reports — HTML/Markdown via Jinja2 with diff sections
- Smart Notifications — Telegram and Discord webhook alerts on changes
- Dockerized Workflow — Multi-stage Docker build,
docker compose up -dfor 24/7 scans
🛠️ Tech Stack
- Language: Python 3.11+
- CLI: Typer
- Terminal output: Rich
- HTTP client: HTTPX
- DB & Storage: SQLite
- Templates: Jinja2
- Config: PyYAML
- Orchestration: subfinder · dnsx · httpx · naabu · nuclei · katana
- Reports: HTML/Markdown via Jinja2 with diff sections
- Notifications: Telegram / Discord webhooks
- Deployment: Docker
🏗️ Architecture
graph TD
S[Scope YAML] --> G{Scope Guard}
G -->|allow| SF[subfinder]
SF --> DX[dnsx]
DX --> HX[httpx]
HX --> NB[naabu]
NB --> NC[nuclei]
NC --> KT[katana]
KT --> SC[secrets]
SC --> DB[(SQLite)]
DB --> DIFF[Diff Engine]
DIFF --> RPT[Report]
DIFF --> NOT[Notifications]
NOT --> TG[Telegram]
NOT --> DC[Discord]
G -->|deny| X[❌ Blocked]
⚡ Quick Start
Prerequisites
- Python 3.11+
- Docker (recommended) or Go tools installed locally
Using Docker (Recommended)
docker compose build
docker compose run --rm bounthunt scan /data/scope.yaml --all
docker compose up -d
Using Source
git clone https://github.com/bess1lie/bounthunt.git
cd bounthunt
pip install .
bounthunt init scope.yaml
bounthunt scan scope.yaml --all
🗺️ Roadmap
| Feature | Status |
|---|---|
| Core Recon Pipeline | ✅ |
| Scope Guard & Diff Engine | ✅ |
| SQLite Persistence | ✅ |
| Docker Deployment | ✅ |
| Real-time Web Dashboard | 🚧 In Progress |
| Custom Notification Templates | 🔮 Planned |
🤝 Contributing
Contributions welcome! See CONTRIBUTING.md.
📄 License
MIT — see LICENSE.
Metadata
Release files for bounthunt 1.1.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 | Actions |
|---|---|---|---|---|
| bounthunt-1.1.0.tar.gz | 139.3 kB | Without provenance | Details for bounthunt-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bounthunt-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for bounthunt-1.1.0-py3-none-any.whl |
Total release size: 174.6 kB
Release files / bounthunt-1.1.0.tar.gz
| Download URL | bounthunt-1.1.0.tar.gz |
|---|---|
| Size | 139.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c19ba8aef89d32545f9c02e296d8507b572717d703690a28c93a7461b1b63bef
|
|
BLAKE2b-256 checksum How to use checksums |
a5d26d0d19e8c5441b538213a03c348a510179688240353be92d10eb87d21081
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / bounthunt-1.1.0-py3-none-any.whl
| Download URL | bounthunt-1.1.0-py3-none-any.whl |
|---|---|
| Size | 35.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc50223b767b346ed3fbd5494779e3f55bbdf72335c09e0d25c0b5aa1c8e422a
|
|
BLAKE2b-256 checksum How to use checksums |
d4374466ffbc16797fa8f6678ab000dc78b80e98f91538399e6b46827af84841
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for bounthunt 1.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.