web2-recon
Web2 recon pipeline — subdomain enumeration (subfinder, Chaos API, assetfinder), live host discovery (dnsx, httpx), URL crawling (katana, waybackurls, gau), directory fuzzing (ffuf), JS analysis (LinkFinder, SecretFinder), continuous monitoring (new subdomain alerts, JS change detection, GitHub commit watch). Use when starting recon on any web2 target or when asked about asset discovery, subdomain enum, or attack surface mapping.
72
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Security
1 critical severity finding. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
E006: Malicious code pattern detected in skill scripts.
What this means
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
Why it was flagged
The document contains high-risk offensive reconnaissance and credential-theft techniques (GitHub dorking, JS secret scanning, trufflehog/SecretFinder usage and automated monitoring) that enable discovery and exfiltration of sensitive keys/tokens and persistent surveillance of targets.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
High likelihood: the workflow instructs runtime fetching/parsing of outsider-controlled free text from public sources (e.g., `curl` to `crt.sh` and ProjectDiscovery APIs, plus historical URLs via `waybackurls`/`gau`) into local text files (e.g., `/tmp/subs.txt`, `/tmp/urls.txt`), which would then be read and potentially ingested by an agent/LLM if the pipeline is connected to one.
- Repository
- shuvonsec/claude-bug-bounty
- Commit
2009594
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.