A modular reconnaissance and vulnerability-testing framework for authorized red-team engagements and bug-bounty research — orchestrating scanning, Nuclei templates, Metasploit verification and OSINT into one workflow, with structured reporting.
RedPhantom brings the noisy, repetitive parts of an assessment under one roof: it enumerates a target or a list of targets, runs template-based vulnerability checks, correlates findings, optionally verifies them against Metasploit modules, and produces a structured JSON report. It is safe-by-default — an --audit dry-run mode lets you see exactly what would run before anything touches the target, and any active-exploitation mode requires explicit, separate confirmation flags.
Warning
This framework is built for professionals operating under written authorization. Its aggressive modes can disrupt or compromise systems. Read Legal & authorized use before running anything, and prefer --audit and --metasploit verify until you know what each option does in your environment.
- Target intake — a single IP/domain (
-t) or a file of targets (-f) - Reconnaissance — port/service enumeration, banner collection, WHOIS and footprinting
- Template-based scanning — Nuclei integration with selectable scan profiles and tags
- Metasploit integration — graded modes:
off,verify(check only), and active modes gated behind an explicit confirmation flag - OSINT — passive reconnaissance across public sources
- Engagement profiles — Red Team and Bug Bounty presets that tune scope and intensity
- Safe dry-run —
--auditplans the run without executing against the target - Rate control — configurable delay between actions
- Structured reporting — JSON output for triage and integration
- Linux (Kali, Parrot or Ubuntu recommended), Python 3.8+
- External tools used when present:
nmap,nuclei, and the Metasploit Framework (for verification modes)
git clone https://github.com/CHDevSec/RedPhaton.git
cd RedPhaton
pip install -r requirements.txtAn installer script (install_blackhat.sh) is provided to pull optional external dependencies on a fresh Kali box.
Start in audit mode to see the plan, then move to a verify-only run before anything active:
# 1) Dry-run: show what would be executed, touch nothing
python3 RedPhantom.py -t target.local --audit
# 2) Recon + Nuclei, verify-only Metasploit, save a report
python3 RedPhantom.py -t target.local --nuclei comprehensive --metasploit verify -o report.json
# 3) A list of in-scope targets, gentle pacing
python3 RedPhantom.py -f scope.txt --delay 2 -o engagement.json| Option | Description |
|---|---|
-t, --target |
Single target (IP or domain) |
-f, --file |
File with a list of targets (one per line) |
-o, --output |
JSON output file |
--audit |
Dry-run: plan the actions without executing them |
--nuclei PROFILE |
Nuclei scan profile (default: comprehensive) |
--nuclei-tags TAGS |
Restrict to specific Nuclei template tags |
--metasploit {off,verify,exploit,aggressive} |
Metasploit mode; verify only checks |
--metasploit-confirm |
Required to arm any active Metasploit mode |
--osint |
Passive OSINT reconnaissance |
--delay SECONDS |
Delay between actions |
--verbose |
Verbose output |
Advanced red-team modes (aggressive, stealth, PoC generation and others) are listed in python3 RedPhantom.py --help. They are off by default, intended only for explicitly authorized engagements, and several require an additional confirmation flag before they will run.
RedPhantom is provided for authorized penetration testing, red-team engagements, bug-bounty programs within scope, and security education. By using it you agree that:
- You will only run it against systems you own or have explicit written permission to test.
- You are solely responsible for staying within the authorized scope and for complying with all applicable laws and program rules.
- The author (CHDevSec) provides this software "as is", assumes no liability, and does not condone any unauthorized or malicious use.
Unauthorized access to computer systems is a crime in most jurisdictions. Be ethical. Be professional. Follow responsible-disclosure practices.
MIT © 2025-2026 Caio Henrique (CHDevSec)
Part of the CHDevSec security tooling — portfolio · LinkedIn