Individual skill

exploiting-dependency-confusion

Identifying and exploiting dependency confusion (substitution) attacks where a package manager resolves an internal dependency name from a public registry instead of the intended private one, leading to attacker-controlled code execution at install time. Activates when testing build pipelines, CI/CD systems, leaked manifests, or any ecosystem (npm, PyPI, NuGet, Maven, Gradle, Go, Cargo, RubyGems) that mixes internal and public package sources.

internal/tools/skills/data/web-application-security/exploiting-dependency-confusion/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 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,315
Repository last updated
Nov 8, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Exploiting Dependency Confusion

## When to Use

- During authorized assessments where you can recover application manifests or lockfiles (`package.json`, `requirements.txt`, `pom.xml`, `*.csproj`, `go.mod`, `Cargo.toml`, `Gemfile`)
- When a target leaks internal package names through public JS bundles, error messages, CI logs, or exposed `.git` directories
- When the build tooling is configured with both internal and public registries and is allowed to pick the "best" version globally
- When testing CI/CD runners that fetch dependencies and hold cloud credentials, signing keys, or deploy secrets
- When you spot `npx <binary>` invocations in repos, docs, or CI definitions (binary-name takeover variant)

## Prerequisites

- **Authorization**: Written engagement scope explicitly permitting publishing test packages to public registries
- **Registry accounts**: npm, PyPI, NuGet, RubyGems accounts for publishing PoC packages