Topic starter
02/08/2026 9:47 am
TL;DR: Supply chain attacks increasingly succeed by abusing install-time trust, mutable pipeline dependencies, compromised maintainer accounts, and emerging agentic toolchains, with attackers exploiting gaps in places teams rarely monitor, according to Aikido. The practical fix is less about one tool and more about layered control over dependency age, commit pinning, scoped access, and auditability across the SDLC.
Editorial analysis by NHI Mgmt Group, based on content published by Aikido: “The practical checklist for defending against supply chain attacks”.
By the numbers:
- Open-source malware detections jumped 73% in 2025.
Key questions
Q: What breaks when install-time trust is too permissive in supply chain security?
A: When install-time trust is too permissive, malicious packages can execute before review, validation, or telemetry has time to intervene.
Q: Why do mutable pipeline dependencies increase supply chain risk?
A: Mutable pipeline dependencies increase risk because the code your pipeline trusts can change after approval if it is referenced by a tag or moving pointer.
Q: How should security teams govern AI agent spend in CI/CD pipelines?
A: They should treat spend governance as a request-level control problem, not a billing review problem.
Practitioner guidance
- Implement package age controls Block installation of newly published dependencies until they have passed a minimum age window, especially for packages that can execute scripts during install.
- Pin pipeline dependencies to immutable SHAs Replace mutable tags with commit SHA references for GitHub Actions and similar pipeline components so trusted code cannot change silently.
- Scope agent permissions tightly Limit what AI agents can read, write, and invoke in CI workflows, and separate untrusted text inputs from privileged execution paths.
Bottom line: Supply chain attacks now succeed by turning trusted install and pipeline paths into execution channels that teams rarely govern tightly enough.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:39 pm
Install-time trust has become a governance boundary, not a convenience layer. Supply chain defenders cannot rely on downstream scanning alone when malicious packages execute within hours of publication. The relevant control question is whether a package is allowed to run before it has earned trust. Practitioners should treat publication age, provenance, and execution delay as part of the control plane, not as operational preferences.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
- 59% of compromised machines in a major 2025 supply chain attack were CI/CD runners rather than personal workstations, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What should teams do after a supply chain dependency is compromised?
A: Teams should treat the compromise as a trust-reset event across the delivery path. That means revoking affected tokens, reviewing registry pushes and CI runs, checking for secret exposure, and replacing any mutable dependency references that may have inherited the same trust path. The goal is to contain propagation before the compromised component is reused elsewhere.
👉 Read our full editorial: Supply chain attack defenses now depend on install and pipeline controls