On 26 August 2025, malicious versions of Nx, a widely used build tool for JavaScript projects, were published to the npm package registry. The attack, tracked as CVE-2025-10894 and nicknamed s1ngularity, stole GitHub and npm tokens, SSH keys and crypto wallet files from anyone who installed them. More than 1,000 valid GitHub tokens were taken, and a follow-up phase made over 5,500 private repositories public.
What is going on
Most modern websites are built from hundreds of small, free code packages downloaded automatically from npm, a public library of such packages. Nx is one of them. Attackers published tampered versions of it under the real name, so developers installed malware without noticing.
The unusual part is how the malware searched the machine. Instead of only scanning folders itself, it called the AI command-line tools the developer already had installed — Claude, Gemini and Q — and ran them with flags that skip the usual permission prompts. It then asked those assistants to find interesting files, such as credential and key files.
Think of a burglar who, instead of searching the house himself, asks the household assistant where the valuables are kept — and the assistant has been told not to ask questions.
Who is affected
This affects developers and agencies who installed the malicious Nx versions published on 26 August 2025, not website visitors or ordinary CMS users. If your site was built or maintained by a freelancer or agency using JavaScript tooling, their machines are the risk point, not your server.
The real damage is second-hand: stolen GitHub, npm and cloud tokens give attackers access to source code and deployment pipelines. That is how private repositories ended up public.
What to do now
- Ask whoever maintains your site to check their lockfiles (
package-lock.json,yarn.lock,pnpm-lock.yaml) for the affected Nx versions. - Rotate GitHub, npm and cloud provider tokens, plus any SSH keys used for deployment, if those versions were present.
- Review your GitHub organisation for repositories that changed from private to public, and for unfamiliar repositories or new access tokens.
- Stop running AI command-line tools with permission-skipping flags; let them ask before reading files or executing commands.
- Check deployment logs for unexpected builds or releases around late August 2025.
How to check your own site
A scan cannot see a developer's laptop, but it can show what leaked credentials or a tampered build may have left behind on your live site. Scantinel's free Website Security Check flags outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you suspect your repository or pipeline was touched, you can run a full scan, which adds exposed-file and secret checks, port and service checks with CVE matching, and active OWASP Top 10 testing — only against sites whose ownership you have verified.
Source: Wiz — s1ngularity supply chain attack, August 2025.
Comments
No comments yet.