Supply Chain Propagation

Expanded Definition

Supply chain propagation describes a failure mode in which a single compromised package, maintainer account, build job, or trusted dependency spreads malicious code or trust abuse across many downstream environments. In NHI security, the concern is not only code injection but also credential theft, token abuse, and compromised automation that can move laterally through CI/CD and package distribution paths. This aligns closely with the OWASP Non-Human Identity Top 10, where weak secret handling and overprivileged machine identities create the conditions for rapid blast-radius expansion.

Definitions vary across vendors on whether the term should include only malware propagation or also fraudulent dependency updates, poisoned build artifacts, and abuse of publishing rights. For NHI Management Group, the operational meaning is broader: any trusted software distribution channel that carries malicious payloads, stolen secrets, or attacker-controlled identity claims into consuming systems. The concept is distinct from ordinary vulnerability spread because the trust relationship itself is the amplifier. The most common misapplication is treating supply chain propagation as a purely endpoint malware problem, which occurs when teams monitor only runtime hosts and ignore package registries, CI runners, and maintainer credentials.

Examples and Use Cases

Implementing controls against supply chain propagation rigorously often introduces release friction, requiring organisations to weigh delivery speed against verification depth, signing discipline, and revocation readiness.

• A compromised npm maintainer account publishes a benign-looking update that later executes credential harvesting in downstream build pipelines, similar in pattern to the Shai Hulud npm malware campaign.
• A GitHub Action dependency is updated with malicious logic that reads repository secrets and exfiltrates them into attacker-controlled infrastructure, echoing the Reviewdog GitHub Action supply chain attack.
• A package maintainer, plugin publisher, or automation account is compromised and the attacker uses that trust to push a worm-like payload across multiple ecosystems, as seen in the Miasma and Hades Supply Chain Worms.
• A malicious integration package for AI tooling quietly steals API keys from development environments, which is a growing concern in the JetBrains Marketplace AI Plugin Campaign.
• Security teams use provenance checks, signed releases, and dependency allowlisting to stop the next stage of propagation before the artifact reaches production.

Why It Matters in NHI Security

Supply chain propagation matters because it turns one identity failure into many system failures. When a service account, publishing token, or CI credential is stolen, an attacker can impersonate trusted automation and spread malicious changes at machine speed. NHIMG research shows how quickly this can scale: The State of Secrets Sprawl 2026 reports that 59% of compromised machines in a major 2025 supply chain attack were CI/CD runners rather than personal workstations. That is a strong warning that propagation often begins inside automation, not at the perimeter.

For governance, the issue is not only detection but containment. If secrets remain valid after exposure, downstream systems continue to inherit risk even after the original compromise is closed. The same report found that 64% of valid secrets leaked in 2022 are still valid and exploitable today, which shows why revocation and rotation must be part of the response model. This is also why the State of Secrets in AppSec is relevant here: remediation delays and fragmented secrets management make propagation harder to stop once trust has been abused. Organisations typically encounter the full cost only after a poisoned dependency or compromised automation account has already distributed the payload across multiple environments, at which point supply chain propagation becomes operationally unavoidable to address.

Related resources from NHI Mgmt Group

• What is supply chain amplification in Agentic AI security?
• How do attackers turn a supply-chain incident into wider NHI compromise?
• When should organisations rotate credentials after a supply chain incident?
• How should security teams reduce the risk of secret theft from npm supply chain attacks?