Supply Chain Attack Recon
External recon for software supply-chain attack surface — package-namespace squatting candidates, dependency-confusion vulnerabilities, GitHub Actions injection openings, container image registry exposure, SBOM mining, internal-package-name leakage, and CI/CD configuration exposure. Reconnaissance and identification ONLY — actual package publishing / typosquat attacks are EXTERNAL-OFFENSIVE and require explicit written sign-off because they can affect the entire npm/PyPI ecosystem. Use when the target has a public GitHub org, when their build artifacts/SBOMs are reachable, when their docker im
Install
npx skills add adriannoes/awesome-agentic-ai --skill supply-chain-attack-recongit clone --depth 1 https://github.com/adriannoes/awesome-agentic-ai.git /tmp/awesome-agentic-ai
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-agentic-ai/cursor-claude-codex/skills/bug-hunter/skills/supply-chain-attack-recon ~/.claude/skills/supply-chain-attack-reconPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## When to use Trigger when: - Target has a public GitHub organization (find via OSINT) - JS bundles reference internal-looking package names (`@target-internal/...`, `target-utils`, `target-shared`) - Build logs, SBOMs, or `package-lock.json` files are publicly accessible - Target uses CI/CD that's partially public (GitHub Actions, GitLab CI, Bitrise) - Docker images on Docker Hub/GHCR/Quay belong to target org - Findings include `npmrc`/`pip.conf`/`gradle.properties` with internal registry URLs - `.github/workflows/*.yml` files reference internal tooling Do NOT use for: - Internal-network artifact registries (out of scope per external boundary) - Actually publishing typosquats / dep-confusion packages without explicit OK - Compromising upstream open-source projects (massive blast radius — illegal in most jurisdictions without authorization) --- ## The supply-chain attack surface map ``` Target Org ├── Public GitHub Org → workflow files → secrets exfil opportunities ├── Internal package names in JS/Android bundles → dependency confusion ├── Docker images on public registries → secrets in layers, RCE on pull ├── SBOM / artifact metadata → exact dep versions for known-vuln chaining ├── npmrc / pip.conf in repos → internal registry URL disclosure ├── External package dependencies → typosquat name candidates └── Build/release pipelines → injection if pull_request_target etc. ``` --- ## Step 1 — GitHub org discovery
Details
- Skill name
supply-chain-attack-recon- Repository
- adriannoes/awesome-agentic-ai
- Path
cursor-claude-codex/skills/bug-hunter/skills/supply-chain-attack-recon/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Supply Chain Attack Recon skill do?
External recon for software supply-chain attack surface — package-namespace squatting candidates, dependency-confusion vulnerabilities, GitHub Actions injection openings, container image registry exposure, SBOM mining, internal-package-name leakage, and CI/CD configuration exposure. Reconnaissance and identification ONLY — actual package publishing / typosquat attacks are EXTERNAL-OFFENSIVE and require explicit written sign-off because they can affect the entire npm/PyPI ecosystem. Use when the target has a public GitHub org, when their build artifacts/SBOMs are reachable, when their docker im
How do I install the Supply Chain Attack Recon skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add adriannoes/awesome-agentic-ai --skill supply-chain-attack-recon. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Supply Chain Attack Recon popular?
It lives in adriannoes/awesome-agentic-ai, which has 100 GitHub stars and 27 forks, and is included in 2 curated skill lists.
Related skills
Browserstack
100adriannoes/awesome-agentic-ai
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
Coverage
100adriannoes/awesome-agentic-ai
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
Fix
100adriannoes/awesome-agentic-ai
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".
Vercel CLI with Tokens
100adriannoes/awesome-agentic-ai
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
Securing API Gateway with AWS Waf
100adriannoes/awesome-agentic-ai
Securing API Gateway endpoints with AWS WAF by configuring managed rule groups for OWASP Top 10 protection, creating custom rate limiting rules, implementing bot control, setting up IP reputation filtering, and monitoring WAF metrics for security effectiveness.
Vercel Optimize
100adriannoes/awesome-agentic-ai
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.