Notifications
Clear all
Topic starter
20/08/2026 5:31 pm
TL;DR: A compromised Nx npm package in the s1ngularity incident stole GitHub and npm tokens, SSH keys, and environment secrets, while also weaponising local AI CLI tools for reconnaissance and exfiltration, according to StepSecurity’s analysis. The case shows that developer supply chain compromise now overlaps directly with NHI governance, secrets hygiene, and tool trust boundaries.
NHIMG editorial — based on content published by StepSecurity: LLMjacking: How Attackers Hijack AI Using Compromised NHIs
By the numbers:
- The attack window lasted approximately 5 hours and 20 minutes, during which 8 malicious versions were published across two major version branches.
Questions worth separating out
Q: What breaks when developer tokens are stolen through a supply chain attack?
A: The main failure is that stolen tokens let attackers act as trusted automation rather than as obvious intruders.
Q: Why do non-human credentials amplify supply chain risk in developer pipelines?
A: Because they are reusable across systems, often over-scoped, and frequently minted in automation contexts that are assumed safe.
Q: How do security teams know whether device revocation is actually working?
A: They should test the full authorisation path, not just the revoke request.
Practitioner guidance
- Treat developer tokens as governed NHI credentials Inventory GitHub, npm, SSH, and similar credentials as non-human identities, assign ownership, and enforce expiry, revocation, and scope review on the same schedule as other machine credentials.
- Disable or restrict install-time scripts where feasible Block automatic execution of post-install hooks for packages that do not need them, and alert on dependency installs that invoke filesystem-wide collection or network activity.
- Constrain AI CLI permissions on developer endpoints Limit which local AI assistants can access files, shell commands, and secrets, and require explicit policy for dangerous flags such as trust-all-tools or permission-skipping modes.
What's in the full analysis
StepSecurity's full blog post covers the operational detail this post intentionally leaves for the source:
- The complete compromise timeline across the initial npm takeover and the second-wave repository exposure activity.
- Detailed indicators of compromise, including filesystem artefacts, token artefacts, and repository naming patterns.
- The full malicious telemetry.js behaviour and the command-line flags used to coerce local AI assistants.
- Step-by-step remediation instructions for affected organisations and package versions.
👉 Read StepSecurity's analysis of the Nx supply chain compromise and AI tool abuse →
Nx supply chain compromise: what it means for developer identity controls?
Explore further
20/08/2026 6:18 pm
This incident confirms that developer secrets are now operational NHI assets, not incidental tooling artefacts. GitHub tokens, npm credentials, and SSH keys all function as machine identities when they authorise API access and repository actions. Once they are treated as interchangeable convenience artefacts, organisations lose control over where privilege begins and ends. The practitioner takeaway is to govern developer credentials as part of the NHI estate, not as a separate dev productivity concern.
A few things that frame the scale:
- 64% of valid secrets leaked in 2022 are still valid and exploitable today, according to The State of Secrets Sprawl 2026.
- 28.65 million new hardcoded secrets were detected in public GitHub commits in 2025 alone, a 34% year-over-year increase and the largest single-year jump ever recorded.
A question worth separating out:
Q: Who is accountable when a package repository compromise exposes enterprise credentials?
A: Accountability sits with the teams that own publishing access, dependency governance, secrets management, and endpoint containment. Frameworks such as OWASP NHI and NIST CSF matter because the failure is not only malware execution, but the absence of lifecycle control over the identities and secrets that the pipeline depended on.
👉 Read our full editorial: Nx supply chain compromise exposed AI tool abuse and secret theft
