Skip to content
Cloud Security Breaches

Nx (Nrwl) (2025): what the sources say about the cloud incident

Nx (Nrwl) disclosed the incident on 26 Aug 2025. What was exposed, as the sources state it: The company's npm publishing token; malicious package versions scanned users' systems and uploaded results to public GitHub repositories. The company stated Nx Cloud was not affected.

Open the ledger · Report a correction

Disclosed
26 Aug 2025
Incident window
August 26, 2025 (malicious packages live for 4 hours)
Cloud or provider
GitHub
What was exposed
The company's npm publishing token; malicious package versions scanned users' systems and uploaded results to public GitHub repositories. The company stated Nx Cloud was not affected.
How access was gained
The post-mortem says attackers exploited a GitHub Actions injection vulnerability to steal the npm publishing token; the repository's workflow permissions were read and write.
Access path
Leaked access keys and secrets; also Over-permissioned identities
Kind of control that addresses it
set CI workflow tokens to read-only by default, avoid running untrusted pull request input with repository secrets, and publish with short-lived trusted-publisher credentials

In the words of the source

“Attackers exploited a GitHub Actions injection vulnerability to steal our NPM publishing token and publish malicious packages for 4 hours.” (provider post mortem, S1ngularity - What Happened, How We Responded, What We Learned)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. S1ngularity - What Happened, How We Responded, What We Learned, read 16 Nov 2026

Last reviewed 16 Nov 2026.