Nx build system malicious package supply-chain attack

Severity: low · CVSS 3.1 · Published 2025-09-25

Malicious versions of the Nx build system and several related npm packages were published containing code that steals credentials from developer machines. The compromised packages scan the file system, harvest sensitive information like API tokens and authentication credentials, and upload them to attacker-controlled GitHub repositories. Developers who installed affected versions should immediately check their GitHub accounts for suspicious repositories and rotate all credentials and tokens.

Technologies: Nrwl Nx. Vendors: Nrwl.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Low severity, with a CVSS score of 3.1, published 25 September 2025.
Which products and versions are affected?
Nrwl Nx 20.9.0, 20.10.0, 20.11.0, 20.12.0, 21.5.0, 21.6.0, 21.7.0, 21.8.0.
Is there a fix for This vulnerability?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is This vulnerability attacked?
It is attacked over the network, in a software library.
Am I affected?
Check whether you run Nrwl Nx at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

This is a supply-chain attack where malicious code was injected into npm packages via a compromised build workflow. The vulnerable workflow was introduced into the Nx repository's CI/CD pipeline, enabling attackers to inject executable code into published packages. The malicious payload performs reconnaissance by scanning the file system, collecting credentials and environment variables, and exfiltrating this data to attacker-controlled GitHub repositories created under the victim's own account (named with "s1ngularity-repository"). The attack requires user interaction (installing the malicious package via npm) but can be triggered automatically during routine dependency updates. All malicious versions have been removed from npm; users should immediately update to the latest version and rotate all credentials (GitHub, npm tokens, and environment variables).

Affected products

  • Nrwl Nx 20.9.0, 20.10.0, 20.11.0, 20.12.0, 21.5.0, 21.6.0, 21.7.0, 21.8.0
  • Nrwl @nx/devkit 20.9.0, 21.5.0
  • Nrwl @nx/js 20.9.0, 21.5.0
  • Nrwl @nx/workspace 20.9.0, 21.5.0
  • Nrwl @nx/node 20.9.0, 21.5.0
  • Nrwl @nx/eslint 21.5.0
  • Nrwl @nx/key 3.2.0
  • Nrwl @nx/enterprise-cloud 3.2.0

Timeline

  • 2025-08-27: disclosed: Malicious packages published and discovered; versions removed from npm by 10:44 PM EDT on the same day
  • 2025-09-24: advisory: CVE-2025-10894 assigned
  • 2025-09-25: other: GHSA-8mjq-32x3-22qf withdrawn as duplicate of GHSA-cxm3-wv7p-598c

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.