Question 1

What Is a Dependency Confusion Attack?

Accepted Answer

A dependency confusion attack exploits a simple ambiguity: when your project depends on a package called auth-utils, which registry does the package manager check first?

Most package managers search public registries by default. If an attacker has published auth-utils on the public registry with a version number higher than your private version, the package manager installs the attacker's package. Your build system pulls in malicious code, thinking it's your own internal library.

The attack is effective because it targets the resolution logic of the package manager itself — not a bug in your code or a vulnerability in a dependency. The package manager is doing exactly what it was designed to do: resolve the highest available version of a package by name.

The term "dependency confusion" was coined by security researcher Alex Birsan in 2021, though the underlying resolution behavior had been known to package manager maintainers for years. What Birsan demonstrated was that this theoretical risk was trivially exploitable at scale against major corporations.

Question 2

Does Your Dependency Scanner Catch This?

Accepted Answer

Let's be direct: traditional CVE-based vulnerability scanners — including GeekWala — are not designed to detect dependency confusion attacks.

GeekWala scans your dependency tree against the OSV database, enriched with EPSS scores and CISA KEV data, to identify known vulnerabilities in the packages you actually use. If a package version has a published CVE, GeekWala finds it and helps you prioritize remediation.

Dependency confusion is a different class of problem. The malicious package won't have a CVE — it was just published by the attacker. There's no advisory to match against. The attack happens at the resolution layer, before the scanner even sees the dependency tree.

For supply chain attack detection, consider specialized tools: Socket (monitors for suspicious package behavior), Phylum (analyzes package risk signals), or Sigstore/Cosign (verifies package provenance). npm's built-in --before flag and npm audit signatures provide additional signals.

The strongest posture combines both approaches: CVE scanning (GeekWala, Trivy, Grype) for known vulnerabilities in legitimate packages, plus supply chain analysis tools for novel attacks like dependency confusion. Neither alone is sufficient. If you're evaluating tools, our dependency scanner comparison covers the CVE scanning side in detail.