Notifications
Clear all
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.
NHIMG editorial — based on content published by Expel: More supply chain compromises: Namaste, xinference, and more
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: How do security teams know if package-based secret theft is happening?
A: Look for unusual DNS activity, recent dependency installs, and new access attempts from accounts that should not be active on the affected endpoint.
Q: Why do compromised packages create such a large identity risk?
A: Because they often run inside environments that already contain reusable secrets, tokens, and service accounts.
Q: What do teams get wrong about secrets in build automation?
A: Teams often assume build secrets are safe because the job is temporary, but the credential usually outlives the run.
Practitioner guidance
- Disable install-time script execution Set package managers to block post-install hooks by default, then allow execution only for explicitly approved dependencies that have been reviewed and pinned.
- Rotate exposed cloud and publishing credentials Assume any key present on a system that loaded a compromised package may be exposed.
- Rebuild from a clean dependency state Clear local caches, remove untrusted artifacts, reinstall from known-safe versions, and verify lockfiles and requirements files for unauthorized changes.
What's in the full analysis
Expel's full blog covers the operational detail this post intentionally leaves for the source:
- The specific malicious package behaviour observed in the npm and PyPI campaigns, including the post-install mechanics and credential harvesting paths
- Indicator of compromise details and file artefacts that security teams can use to confirm exposure in developer environments
- Step-by-step response actions for clearing caches, rebuilding environments, and validating whether package-lock or requirements files were altered
- Source references to the underlying JFrog and Socket research for teams that need to trace the compromise chain more deeply
👉 Read Expel's analysis of the npm and PyPI supply chain compromises →
Supply chain package compromises: what IAM teams need to do now?
Explore further
19/08/2026 4:12 pm
Package trust is now an identity boundary. The practical mistake is treating dependency installation as a software-only concern when it is also a secrets-exposure event. Malicious install hooks can inherit whatever non-human identities are present in the build environment, including cloud keys and publishing credentials. That means software supply chain governance and NHI governance now overlap directly, especially where developer automation has standing privilege. Practitioners should treat package execution as a governed access decision, not a harmless install step.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.
A question worth separating out:
Q: How can organisations reduce blast radius after a package compromise?
A: Separate credentials by function, make them short-lived, and avoid reusing the same secret across build, test, publish, and runtime workflows. If one package is compromised, the attack should not be able to move from a local install into cloud access or software publishing.
👉 Read our full editorial: Npm and PyPI supply chain attacks are stealing cloud credentials
