On August 26, 2025, attackers compromised npm publishing credentials for the Nx project. Malicious versions were briefly published to npm that exfiltrated developer credentials and created unauthorized GitHub repositories (s1ngularity-repository-*). Although npm quickly removed the malicious versions, the compromise has broader downstream implications.
What Happened During the Attack
- Attackers briefly published malicious versionsof Nx packages to npm by using compromised publishing keys.
- Nx maintainers confirmed the publishing tokens were stolen, likely through phishing or token leakage, since npm still allowed static Personal Access Tokens (PATs) instead of enforcing trusted publishing.
- Malicious versions (e.g.,
nx@20.9.0, nx@21.5.0, @nx/devkit@21.5.0) were pushed between 6:30–8:30 PM EDT before being removed.
Developers didn’t even need to install Nx directly. VS Code / Cursor extensions (Nx Console) auto-fetched @latest from npm during the attack window, silently pulling malicious versions. This meant simply opening VS Code could trigger the infection.
Although npm quickly removed the malicious versions, the compromise has broader downstream implications. Unfortunately, removing the malicious version just hides the problem as those credentials are still out there.
The malware:
- Created repos like s1ngularity-repository-0 in victims’ GitHub accounts.
- Exfiltrated API tokens, GitHub/npx credentials, SSH keys, and local text files.
- Modified .bashrc / .zshrc to insert malicious commands.
Why This Matters
The domino effect on downstream (and very possibly unaware) victims is how supply chain attacks continue: a single stolen publishing token cascades into compromised developers, companies, and critical repositories, ultimately impacting the global open-source ecosystem. Even after malicious packages are removed, credential leakage persists, leaving long-term risk:
Downstream supply chain risk: Developer tokens often provide access to private repositories, CI/CD pipelines, and software release processes. If left active, they could enable attackers to move laterally into enterprise systems or compromise upstream projects.
Breadth of exposure: The affected accounts span a wide range of companies, from software vendors to financial services to healthcare, meaning potential ripple effects across the broader ecosystem.
Relevance to you: Even if you don’t use Nx directly, your dependencies or vendors may rely on it or employ developers whose accounts were compromised. That creates a vector for indirect supply chain impact.
The Nx compromise reinforces that supply chain security is collective security. A single weak credential can ripple outward to thousands of repositories, affecting enterprises worldwide.
Exiger will continue mapping the potential “blast radius” of this incident to determine which companies and repositories may be at risk of downstream compromise.
How Exiger Helps
- Mapping Exposure: linking compromised accounts to companies and industries
- Prioritizing Risk: focusing on the most impactful repos and contributors
- Actionable Intelligence: giving clients data to take immediate steps
- Contextualizing Threats: showing how one compromised maintainer cascades across the ecosystem
Access to Full Data
Exiger has compiled the complete list of:
- 1,100 compromised developers
- 370 companies & their industries
- 390 directly at-risk repos
- 10,900 previously contributed repos (>10 stars)
We can share this dataset with clients on request to support internal assessments and targeted risk reviews.
