SecurCheckCyber Center
Need help
Back to analysis tools
All cyber threats
Infrastructure

Dependency compromise

Compromised software dependency, supply-chain package compromise

An attacker compromises a third-party library or component that is then delivered to downstream applications.

Fiche de sensibilisationPrête à diffuser à vos équipes ou clients

MIGHT YOU BE AFFECTED?

Turn knowledge into action.

How does this work?

Malicious code can enter a trusted project through a hijacked maintainer account, compromised release pipeline or altered package, then spread when consumers install what looks like a legitimate update.

REAL-WORLD EXAMPLE

« A new version of a popular package secretly reads environment variables and sends credentials to an external server during installation. »

Typical sequence

  1. 1The attacker gains control of a package, maintainer identity or publishing workflow.
  2. 2They introduce malicious changes into an otherwise trusted dependency.
  3. 3Downstream builds install or execute the compromised release.
  4. 4The payload gains access to application secrets, build systems or runtime data.

Warning signs

  • Unexpected network traffic or scripts after a dependency update.
  • A sudden publisher or maintainer change without an explanation.
  • Software-bill-of-materials or package-integrity alerts.
  • New installation hooks, permissions or code unrelated to the package's purpose.

How to protect yourself

  • Pin and verify dependency versions and package integrity.
  • Maintain an SBOM and scan third-party components and provenance.
  • Review high-risk updates, installation scripts and maintainer changes.
  • Use isolated builds with minimal secrets and controlled release approvals.

If you think you are affected

Block the affected dependency version, identify every build and system that used it and preserve artefacts. Rebuild from verified sources, revoke exposed secrets and investigate potential downstream compromise.

Get help

Last updated: 8 October 2026