Notifications
Clear all
Topic starter
18/08/2026 2:22 pm
TL;DR: On May 11, 2026, a coordinated supply-chain attack published malicious versions of at least 235 packages across npm and PyPI, with install-time payloads stealing AWS, GitHub, Vault, and CI tokens, according to FOSSA. The incident shows that package installation itself has become an identity exposure point when non-human credentials are reachable from developer and build environments.
NHIMG editorial — based on content published by FOSSA covering the Mini-Shai-Hulud supply-chain attack: malicious npm and PyPI packages and remediation guidance
By the numbers:
- A coordinated supply-chain attack published malicious versions of at least 235 packages across npm and PyPI.
- The attack first compromised 42 @tanstack/* npm packages before spreading to Mistral AI, UiPath, OpenSearch, Guardrails AI, and others.
- The @uipath/* cluster alone included 65 malicious packages, showing how scoped brand takeover can accelerate package trust abuse.
Questions worth separating out
Q: What breaks when a compromised package can read secrets during installation?
A: The main failure is that package installation becomes an identity event.
Q: Why do NHIs make supply-chain attacks harder to contain?
A: NHIs are often present in many places at once, including developer laptops, build agents, and CI pipelines.
Q: What do security teams get wrong about package-level secret exposure?
A: Teams often focus on whether the package is malicious and miss whether the environment is exposed.
Practitioner guidance
- Restrict package script execution Disable or tightly control install-time hooks such as preinstall and prepare in build pipelines where possible, and run package installs in isolated environments that do not contain cloud credentials or developer tokens.
- Inventory exposed NHI secrets Search developer laptops, CI runners, and container images for AWS IAM credentials, GitHub PATs and OIDC tokens, Vault tokens, npm publish tokens, and Kubernetes service-account tokens that could be reached by package code.
- Rotate the credential classes named in the attack Prioritise rotation of cloud keys, GitHub tokens, CI tokens, and Vault tokens on any host or pipeline that could have executed the malicious packages, then revoke unused secrets and shorten TTLs.
What's in the full article
FOSSA's full post covers the operational detail this analysis intentionally leaves at the governance level:
- Package-by-package remediation guidance for the affected npm and PyPI ecosystems
- Detection workflow details for FOSSA-tracked repositories and Malware issues
- Specific credential rotation steps for AWS IAM, GitHub, npm publish, and Vault tokens
- File and log paths to inspect in developer environments and CI build records
👉 Read FOSSA's analysis of the Mini-Shai-Hulud supply-chain attack and NHI exposure →
Mini-Shai-Hulud supply chain attack: what identity teams need to know?
Explore further
18/08/2026 3:14 pm
Package installation is now an identity event, not just a software event. This attack worked because install-time execution had access to credentials that should have been isolated from untrusted package code. NHI governance has to extend into developer and build environments, because the compromise path was credentials, not source code alone. Practitioners should treat dependency execution as a governed access decision.
A few things that frame the scale:
- From our research: 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, according to The State of Non-Human Identity Security.
A question worth separating out:
Q: How should teams respond when malicious packages are found in build systems?
A: Contain the affected pipelines first, then rotate every credential class that may have been accessible to package code, including cloud keys, CI tokens, and publish tokens. After that, inspect developer tooling for persistence and verify whether any downstream repositories or artifacts were built while the malicious package was present.
👉 Read our full editorial: Mini-Shai-Hulud shows how package installs can steal NHI secrets
