TL;DR: Trusted npm and PyPI packages such as Trivy, LiteLLM and Checkmarx KICS let malicious code reach credentials and runtime environments, Intel 471 reports. Cloud-native and DevOps pipelines need tighter execution boundaries because inherited package trust can extend a compromise far beyond the package itself.
Editorial analysis by NHI Mgmt Group, based on content published by Intel 471: “TeamPCP Supply Chain Attacks”.
Key questions
Q: Why do supply chain attacks create such large blast radius?
A: They create large blast radius because one upstream compromise can be reused across many downstream relationships.
Q: How do security teams know whether dependency trust is being overextended?
A: Warning signs include packages that run arbitrary scripts, runners that can reach secrets by default, and shared tokens that work across build, deploy and publish stages.
Q: What breaks when a malicious package can execute inside a trusted runtime?
A: The boundary between software delivery and identity access breaks first.
Practitioner guidance
- Constrain package execution at install time Block or sandbox package scripts where they are not required, and review where installation-time code can reach secrets or cloud credentials.
- Reduce privilege on build and runner identities Separate publishing, build and deployment permissions so CI/CD identities cannot freely access secrets, registries and production systems.
- Inventory packages that can touch sensitive workflows Map which packages are used in build pipelines, developer tooling and AI-assisted workflows, then flag those with broad execution reach.
Bottom line: The core risk is not simply malicious code in a package, but the way trusted dependencies can inherit execution rights and reach sensitive credentials.
Glossary terms: Blast Radius, Software Supply Chain Attack, Build Runner Identity, Dependency Update Trust Boundary
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Software supply chain trust is now an identity control problem. When a package repository becomes the entry point, the practical question is no longer only whether code is malicious. It is whether the consuming environment lets that code inherit credentials, deployment reach or human trust without sufficient boundaries. That makes provenance, signing and execution isolation part of identity governance for modern delivery pipelines.
A few things that frame the scale:
- 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.
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
A: Secret containment should come first when packages can execute code inside trusted workflows, because exposed tokens convert a package event into an environment compromise. Provenance controls still matter, but if credentials remain broadly accessible, a verified package can still be abused after installation.
👉 Read our full editorial: TeamPCP supply chain compromise expands credential theft blast radius