hunt-source-leak
Hunt source code and build artifact leakage — JavaScript source maps (.js.map) reconstructing TypeScript/ES6 source, Swagger/OpenAPI JSON endpoint discovery, .env/.git exposure, webpack chunks with hardcoded secrets, robots.txt/security.txt recon, build-info files, asset-manifest.json API route discovery, .DS_Store file listing. Use at the START of every recon session — these findings often unlock the entire attack surface.
68
82%
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
3 findings: 2 critical severity, 1 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
E005: Suspicious download URL detected in skill instructions.
What this means
Detected a suspicious URL in the skill instructions that could lead the agent to download and execute malicious scripts or binaries. This includes links to executables from untrusted sources, typosquatting of official packages, URL shorteners that obscure the destination, and personal file hosting services.
Why it was flagged
These URLs point to exposed build artifacts and .git/.DS_Store endpoints (asset manifests, Next.js build manifests, and accessible .git/HEAD) that enable source reconstruction and secret discovery, representing a high security risk.
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
This document is an explicit offensive playbook for locating and extracting sensitive secrets (source maps, .env, swagger, exposed .git, build artifacts) and includes concrete commands and tooling to reconstruct repos and harvest credentials, enabling data exfiltration and credential theft.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The skill explicitly instructs downloading .env, source maps, git history and JS bundles and then printing/grepping their contents (head, echo, grep, git-dumper, trufflehog, base64 decode), which requires the LLM/operator to handle and output any discovered secrets verbatim, posing a direct exfiltration risk.
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
The required workflow in SKILL.md fetches arbitrary runtime content from an external target (e.g., via `curl` to `/.env`, `/swagger.json`, `/_next/static/.../*.js`, and `*.map`), then ingests that retrieved (outsider-authored) free-form text into local files and proceeds to parse/grep it for secrets—so it can enter the agent/LLM context indirectly if the tool outputs or retrieved excerpts are included in the LLM prompt.
- Repository
- elementalsouls/Claude-BugHunter
- Commit
6b9c96e
- 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.