/scan-cves
Run a focused nuclei CVE sweep against a host or recon directory, optionally filtered by year. Runs log4j-scan in parallel when installed for legacy enterprise stacks. Usage: /scan-cves <host-or-file> [--year 2024] | /scan-cves --recon <recon-dir>
$ npx -y skills add shuvonsec/claude-bug-bounty --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/scan-cves
Context preview
What this command does when you run it.
Run a focused nuclei CVE sweep against a host or recon directory, optionally filtered by year. Runs log4j-scan in parallel when installed for legacy enterprise stacks. Usage: /scan-cves <host-or-file> [--year 2024] | /scan-cves --recon <recon-dir>
Command definition
scan-cves.mddescription: Run a focused nuclei CVE sweep against a host or recon directory, optionally filtered by year. Runs log4j-scan in parallel when installed for legacy enterprise stacks. Usage: /scan-cves <host-or-file> [--year 2024] | /scan-cves --recon <recon-dir>
/scan-cves
Targeted nuclei scan of the `cve/` template directory plus optional log4j-scan.
Usage
/scan-cves https://target.com
/scan-cves --recon recon/target.com
/scan-cves --year 2024 recon/target.com/live/urls.txt
Why a separate command
`/recon` already runs a broad nuclei phase across every severity — this command narrows to **known CVEs only**, which:
- Cuts the runtime by an order of magnitude (high/critical CVE templates only).
- Surfaces signals that pay even on dormant programs (CVE-2021-44228 still hits
on legacy enterprise hosts).
- Lets you re-scan one or two URLs without rerunning the full pipeline.
Set `NUCLEI_NO_UPDATE=1` to skip the template update on each run when iterating quickly.
Output
`findings/cve/<timestamp>/`:
- `nuclei_cve.jsonl` — one finding per line (template ID, host, severity)
- `log4j.txt` — optional log4j-scan output when the scanner is installed
After a hit
1. Confirm the version manually (don't trust the template — show the response). 2. Check program scope and reward table; many CVEs are explicitly out-of-scope if the program already disclosed them or is mid-patch. 3. Provide a non-destructive PoC: a single request that proves the version is vulnerable, not a working exploit chain.
Read more
description: Run a focused nuclei CVE sweep against a host or recon directory, optionally filtered by year. Runs log4j-scan in parallel when installed for legacy enterprise stacks. Usage: /scan-cves <host-or-file> [--year 2024] | /scan-cves --recon <recon-dir>
/scan-cves
Targeted nuclei scan of the `cve/` template directory plus optional log4j-scan.
Usage
/scan-cves https://target.com /scan-cves --recon recon/target.com /scan-cves --year 2024 recon/target.com/live/urls.txt
Why a separate command
`/recon` already runs a broad nuclei phase across every severity — this command narrows to **known CVEs only**, which:
- Cuts the runtime by an order of magnitude (high/critical CVE templates only).
- Surfaces signals that pay even on dormant programs (CVE-2021-44228 still hits
on legacy enterprise hosts).
- Lets you re-scan one or two URLs without rerunning the full pipeline.
Set `NUCLEI_NO_UPDATE=1` to skip the template update on each run when iterating quickly.
Output
`findings/cve/<timestamp>/`:
- `nuclei_cve.jsonl` — one finding per line (template ID, host, severity)
- `log4j.txt` — optional log4j-scan output when the scanner is installed
After a hit
1. Confirm the version manually (don't trust the template — show the response). 2. Check program scope and reward table; many CVEs are explicitly out-of-scope if the program already disclosed them or is mid-patch. 3. Provide a non-destructive PoC: a single request that proves the version is vulnerable, not a working exploit chain.
AI-powered bug bounty hunting from your terminal - recon, 20 vuln classes, autonomous hunting, and report generation. All inside Claude Code.
Repo: shuvonsec/claude-bug-bounty
Other commands on claude-bug-bounty.
- /arsenal
Show which external bug-bounty tools are installed on this machine and print install hints for the missing ones. Curated from high-signal repos. Use to bootstrap a fresh box or audit which optional capabilities are wired in. Usage: /arsenal | /arsenal <tool-name>
Open command - /autopilot
Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo]
Open command - /breach-check
HIBP k-anonymity check on a password wordlist. Enriches each password with its breach count, ranks DESC. Free API (no key), only first 5 chars of SHA-1 sent. Output -> <input>-ranked.txt. Usage /breach-check <wordlist> [--min-count N] [--max-count N] [--with-counts]
Open command - /bypass-403
Probe a 403/401 endpoint with the most-paid bypass tricks (header injection, path encoding, method swap, WAF fingerprint, vendor-specific). Wraps byp4xx when installed; otherwise runs a built-in matrix of 38+ techniques. Usage: /bypass-403 <url> | /bypass-403 -l <urls-file>
Open command - /chain
Build an exploit chain — given bug A, finds B and C to combine for higher severity and payout. Knows common chain patterns: IDOR→ATO, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth. Usage: /chain
Open command - /cloud-recon
Sweep cloud assets for a target — public S3/Azure/GCP buckets via S3Scanner and cloud_enum, plus CloudFlare-bypassed origin IPs via CloudFail (or built-in DNS-history fallback). Use --keyword for storage discovery and --cf-bypass to find an origin IP behind CloudFlare. Usage:
Open command