CyberKit

Dependency Confusion

Also called Namespace Confusion.

Hijacking a build by publishing a public package that shadows a private one.

What it is

A supply-chain attack that exploits package managers preferring a higher-version public package over a private internal one of the same name, so an attacker's malicious public package is pulled into a build instead of the intended internal dependency.

Why it matters

It can deliver attacker code straight into a trusted build pipeline with no user interaction, making it a serious software supply-chain risk that DFIR may trace through build logs and lockfiles.

In practice

Publishing a public package matching an internal module's name at a higher version so the build resolves to it.

What to look for

  • Public packages with the same name as your internal ones.
  • Build logs pulling from a public registry unexpectedly.
  • Higher version numbers than you publish.

Common mistake

Leaving package names unscoped. Use scopes and pin your registry.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Trivy Open source

    Scans images, file systems and code for known vulnerabilities and secrets.

  • Falco Open source

    Detects suspicious behavior inside running containers and Kubernetes.

  • Sigstore Open source

    Signs and verifies software artifacts so you can prove where a build came from.

  • CrowdStrike Falcon Cloud Security Commercial

    Protects cloud workloads and containers, from build to runtime.

Read next

  • Web Shell: A malicious script on a web server giving remote command access.
  • Input Validation: Checking that incoming data matches expected type, format, and range.
  • API Security: Protecting application programming interfaces from abuse and data exposure.

Sources