Individual skill
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 images are on Docker Hub/GHCR, or when you find internal package names in their JS bundles.
skills/supply-chain-attack-recon/SKILL.md
Source commit 961a0dd3d2d2f66a07a416ade3b1d4473b64802e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,011
- Repository last updated
- Nov 5, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agent Repository topic
- appsec Repository topic
- bug-bounty Repository topic
- cybersecurity Repository topic
- devsecops Repository topic
- exploit-validation Repository topic
- hermes-agent Repository topic
- infosec Repository topic
- llm-security Repository topic
- nuclei Repository topic
- devops Derived category
- engineering Derived category
- devops-containers Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytesSKILL.mdcore · 42,450 bytes
Read excerpt
## 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