What happened
Malware Ran Developers' AI Tools With Prompts Switched Off
- Flags: the malware passed --dangerously-skip-permissions, --yolo and --trust-all-tools.
- Exposure: more than 2,000 verified secrets leaked, and later waves made more than 6,700 private repositories public.
- Entry: a GitHub Actions flaw let the attacker steal Nx's npm publishing token.
- Refusals: about a quarter of Claude requests were refused.
Timeline
Live for Four Hours, Three Waves Over Five Days
| Date | Event | Source |
|---|---|---|
| August 26, 2025 | Malicious version 21.5.0 is published to npm | StepSecurity |
| August 27, 2025 | A community member opens a GitHub issue and npm removes all affected versions | StepSecurity |
| August 28, 2025 | A second wave uses stolen credentials to make private repositories public | Wiz |
| September 5, 2025 | Nx publishes its postmortem | Nx |
Controls that failed
Permission Prompts Could Be Skipped by a Flag
| Control | Company | What failed | 137AI page |
|---|---|---|---|
| CI workflow security | Nx | A workflow injection flaw let the attacker steal the npm token | Supply Chain of Updates |
| Permission prompts in AI tools | Users and tool makers | Command-line flags skipped every approval prompt | Access and Authorization |
Reporting
A CVE Was Assigned; No Breach Filing Was Found
| Rule | Status | Why |
|---|---|---|
| CVE program | Voluntary | A CVE was assigned for the malicious versions |
| California SB 53 | Not in force | The law took effect in January 2026 |
Every rule tracked is on Incident Reporting Rules and Registries.
Response
Nx Locked Down Publishing
- Regulators and courts: None reported.
- Remediation: Nx moved to npm trusted publishing with two-factor approval and provenance checks; npm removed the versions about four hours after publication.
Record
Incident Record
- Incident ID
- 2025-08-NX-S1NGULARITY
- AI Incident Database
- Incident 1210
- Sources
- Nx postmortem (September 2025); StepSecurity (August 2025); Wiz (2025); NVD CVE-2025-10894
- Last verified
- October 2026