Topic starter
19/08/2026 3:28 pm
TL;DR: Two active supply chain attacks are targeting npm and PyPI packages, with Expel reporting malicious post-install code that steals cloud and SSH credentials from developer and runtime environments. The pattern shows how package trust can collapse into credential theft across the software delivery chain, making clean install discipline and credential governance mandatory.
Editorial analysis by NHI Mgmt Group, based on content published by Expel: “More supply chain compromises: Namaste, xinference, and more”.
Key questions
Q: What breaks when npm or PyPI packages can run install-time code on developer systems?
A: The trust boundary breaks because dependency installation becomes code execution with access to local files, environment variables and secrets.
Q: Why do package compromises often lead to credential theft?
A: Package compromises often lead to credential theft because developers and build hosts commonly store access tokens, cloud keys, and SSH material in reachable locations.
A: Look for unexpected package modifications, unauthorized version publishing, unusual access from developer identities, and dependency changes that appear after a seemingly normal install event.
Practitioner guidance
- Disable package script execution by default Turn off post-install and lifecycle scripts in development and build environments unless a package has been explicitly reviewed and required for a specific workflow.
- Rotate exposed cloud and SSH credentials immediately Assume AWS, Azure, Google Cloud, SSH and Kubernetes secrets on affected systems may be compromised and revoke or reissue them before further use.
- Separate publishing credentials from build credentials Keep package publication tokens, cloud access keys and runtime secrets in different stores with different identities so one compromise cannot write back into the supply chain.
Bottom line: Package compromise now functions as an identity attack because malicious dependencies can reach cloud keys, SSH keys and Kubernetes secrets during normal installation and execution.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:12 pm
Package trust has become a credential governance problem: supply chain security can no longer stop at code integrity checks. When package managers execute installer code, the real control question is which credentials are present at runtime and whether they are isolated from untrusted dependencies. Practitioners should treat dependency execution as an identity event, not only a software delivery event.
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.
A question worth separating out:
Q: When should teams prioritize dependency script controls over broader build hardening?
A: Prioritize them immediately when package managers are allowed to execute code in environments that also hold production-adjacent credentials. Script controls matter most where build hosts, developer laptops or CI runners can see secrets that would be dangerous if exposed. If install-time execution is permitted, stronger build hygiene elsewhere will not fully contain the risk.
👉 Read our full editorial: Npm and PyPI supply chain attacks are stealing cloud credentials