detect-dependency-confusionlisted
Install: claude install-skill umbrasec-labs/umbra-blue
# Dependency Confusion and Namespace Takeover - Defensive Methodology
> **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the log sources and signals, and the hardening, and points to public rule sources. Promotion to Tier 1 (a sourced, tuned UMBRASEC rule) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet.
## TL;DR
Dependency confusion exploits a resolver that can reach both a private registry and a public one. When the private registry does not have a package, or when the public copy carries a higher version, the build silently pulls the public artifact. An attacker who learns an internal package name registers it publicly and waits for a build to install it. Two signals carry the whole detection and neither needs you to decrypt anything: **namespace takeover** (a name in your internal package inventory suddenly exists on the public registry, often brand new, published by an unknown author, with an absurdly high version) and **resolver-order flip** (a package that resolved from your private registry in the last build now resolves from the public upstream, visible as a lock-file `resolved` URL change or a private-registry miss immediately followed by an upstream fetch). Install-time scripts then beacon out, so an unexpected child process or DNS lookup from a bui