Skip to main content
Definition Website Computer and Technology

Supply Chain Attack

Subject: Computer and Technology noun /səˈplaɪ ˌtʃeɪn əˈtæk/ 1 definition

  1. Definition (noun)

    Entry #338 · Updated

    A Supply Chain Attack is a cyberattack that targets a trusted upstream vendor, component, or delivery mechanism to gain unauthorized access or inject malicious code into downstream systems. Rather than breaching a hardened target's perimeter directly, adversaries compromise third-party libraries, build servers, code-signing keys, update channels, or hardware firmware before those artifacts reach end users. Because organizations and package managers routinely verify and deploy signed updates and transitive dependencies from established suppliers, the malicious payload inherits implicit trust and propagates widely across many victims at once. Unlike isolated endpoint exploits or direct social engineering against a single organization, a supply chain attack exploits the shared dependency graph itself—making Software Bills of Materials (SBOMs), cryptographic provenance attestations, pinned dependency hashes, and least-privilege CI/CD pipelines essential defenses.

    Common Types

    • Package Registry Abuse: Publishes malicious artifacts to public registries such as npm or PyPI via typosquatting or dependency confusion, tricking package managers into fetching attacker-controlled code.

    • Upstream Maintainer and Repository Compromise: Hijacks legitimate maintainer accounts or injects concealed backdoors into established open-source libraries or commercial SDKs so downstream applications ingest tainted code during routine updates.

    • Build Pipeline and Update Compromise: Infiltrates CI/CD runners, artifact repositories, or code-signing infrastructure to tamper with compiled binaries and distribute Trojanized updates carrying valid vendor signatures.

    • Hardware and Firmware Tampering: Alters integrated circuits, UEFI firmware, or peripheral device controllers during manufacturing or physical transit to establish persistent, operating-system-independent backdoors.

    Example

    An attacker compromises an open-source maintainer's account and publishes version 2.4.1 of a logging package to the npm registry with a hidden postinstall script that reads AWS_SECRET_ACCESS_KEY and GITHUB_TOKEN from process.env and exfiltrates them over HTTPS. When downstream services resolve "^2.4.0" via npm install inside unisolated CI/CD runners without lockfile pinning or outbound firewall rules, the build pipelines automatically execute the poisoned hook and leak deployment credentials.