Details may change as reporting changes. Information comes from the linked sources, and we do not guarantee it is complete or current.
In plain English
Nx is a popular tool developers install through npm, a giant public shop for code packages. Attackers got a poisoned version of Nx published there. Anyone who installed it ran the attackers' code.
That code searched the computer for valuable secrets such as access keys for GitHub and npm. In its first version it also tried to borrow AI tools already installed on the computer, such as Claude, Gemini and Amazon Q, by running them with the safety questions switched off, so the AI would help search the files.
The stolen data was posted to public repositories on the victims' own GitHub accounts. So the secrets were not only stolen, they were publicly visible until GitHub disabled those repositories.
Words used here
- npm
- A public library of code packages that developers download.
- Package
- A bundle of someone else's code that your project uses.
- SSH key
- A secret file that lets you log in to servers without a password.
- CI / GitHub Actions
- Automatic robots that test and release code when something changes.
What happened
According to Nx's GitHub security advisory (GHSA-cxm3-wv7p-598c), malicious versions of the nx package and some plugins were published to npm. The code scans the file system, collects credentials and posts them to GitHub as a repository under the user's account.
The advisory says the root cause was a vulnerable automated workflow in the Nx repository that allowed code injection.
Wiz reports that the malware used AI command-line tools, including Claude, Gemini and Amazon Q, with permission-skipping flags to help search files. Wiz saw this succeed in hundreds of cases, though AI providers' safeguards sometimes stopped it.
Wiz reports GitHub disabled the attacker-created repositories on August 27, 2025.
How it unfolded
- August 26, 2025
Malicious versions are published to npm.
- August 27, 2025
The advisory is published, and the packages are removed. GitHub disables attacker-created repositories.
Who was affected
People and systems that installed the affected versions. Wiz observed over a thousand valid GitHub tokens, dozens of valid cloud and npm credentials, and roughly twenty thousand leaked files. Counts differ between sources.
What the response was
- Nx removed the packages and published an advisory with steps to check your GitHub audit log.
- GitHub disabled the attacker-created repositories.
- Users were told to rotate every credential on affected machines.
What went wrong
- A vulnerable automated workflow let an attacker get publishing access.
- Secrets sat in files on developer machines where malware could find them.
- AI tools with permission-skipping modes were usable by the malware.
What worked
- The packages were removed quickly, and the advisory gave a clear way to check if you were affected.
What a small team should do differently
- Do not leave long-lived secrets in files on your computer.
- Avoid permission-skipping modes in AI tools. Keep approval prompts on.
- Lock dependency versions and delay installing brand-new releases.
What you can do today
- Open GitHub, then Settings, then Security log, and look for a project with "s1ngularity" in its name. If you find one, treat your keys and logins as stolen.
- If you used the affected Nx versions, rotate GitHub, npm, cloud and AI keys from a clean device.
- Check your AI tools' settings and turn off any "skip permissions" option.
Official help for the platforms involved
The lesson to take away
Installing a package runs someone else's code with your permissions. Keep secrets out of reach and your AI tools on a short leash.
Sources
- Nx GitHub security advisory GHSA-cxm3-wv7p-598cNx / GitHub, Aug 27, 2025
- Wiz: s1ngularity supply chain attackWiz
Finished this one?
Add it to What I learned and earn 40 Trust. You can open your list from the badge at the bottom of the page.