{
 "slug": "nx-s1ngularity-npm-malware-ai-cli-wallet-search-aug-2025",
 "title": "Compromised Nx npm packages ran victims' AI command-line tools to hunt for wallet and keystore files",
 "url": "https://drains.watch/i/nx-s1ngularity-npm-malware-ai-cli-wallet-search-aug-2025",
 "json": "https://drains.watch/i/nx-s1ngularity-npm-malware-ai-cli-wallet-search-aug-2025.json",
 "status": "closed",
 "severity": "critical",
 "threatStatus": "contained",
 "verification": "verified",
 "ai": {
  "role": "ai-malware",
  "note": "The malware ran locally installed AI CLIs (Claude, Gemini, Amazon Q) to inventory wallet, keystore and secret files for theft; Wiz found the AI step worked in under a quarter of cases and saw no successful crypto exfiltration."
 },
 "chains": [
  "multi-evm"
 ],
 "method": "supply-chain",
 "product": "Nx build system on npm",
 "tags": [
  "multi-evm",
  "supply-chain",
  "nx",
  "npm",
  "s1ngularity",
  "ai-cli",
  "claude-code",
  "gemini-cli",
  "amazon-q",
  "keystore",
  "github-tokens",
  "github-actions",
  "infostealer",
  "wiz",
  "ai"
 ],
 "amountUsd": null,
 "victims": 1700,
 "startedAt": "2025-08-26",
 "closedAt": "2025-09-06",
 "updatedAt": "2025-09-06T12:00:00Z",
 "summary": "Around 26 August 2025 malicious versions of Nx, a widely used JavaScript build tool, were published to npm and stole GitHub and npm tokens on install. The malware also looked for installed AI command-line tools (Claude, Gemini and Amazon Q) and ran them to search the disk for crypto wallet and keystore files, .env files and SSH keys, then published the results to repos in the victim's own GitHub account. Wiz counted over 1,700 users with leaked secrets and over 6,700 private repos made public, but saw no successful crypto theft, partly because the AI tools often refused. Anyone who installed the bad versions should rotate tokens and move funds from wallet files on that machine.",
 "timeline": [
  {
   "date": "2025-08-26",
   "title": "News broke that malicious Nx versions on npm were stealing tokens and using local AI CLIs to search for wallet and secret files.",
   "sourceUrl": "https://www.wiz.io/blog/s1ngularitys-aftermath"
  },
  {
   "date": "2025-08-26",
   "title": "Malicious Nx versions with a data-stealing postinstall script were published to npm.",
   "sourceUrl": "https://www.bleepingcomputer.com/news/security/ai-powered-malware-hit-2-180-github-accounts-in-s1ngularity-attack/"
  },
  {
   "date": "2025-09-03",
   "title": "Wiz published its analysis: over 1,700 users had secrets leaked, over 6,700 private repos were exposed, and no successful crypto exfiltration had been seen.",
   "sourceUrl": "https://www.wiz.io/blog/s1ngularitys-aftermath"
  },
  {
   "date": "2025-09-06",
   "title": "BleepingComputer reported Wiz's tally of 2,180 exposed accounts and 7,200 repositories across three phases.",
   "sourceUrl": "https://www.bleepingcomputer.com/news/security/ai-powered-malware-hit-2-180-github-accounts-in-s1ngularity-attack/"
  }
 ],
 "sources": [
  {
   "kind": "writeup",
   "title": "s1ngularity's Aftermath: AI, TTPs, and Impact in the Nx Supply Chain Attack",
   "url": "https://www.wiz.io/blog/s1ngularitys-aftermath",
   "publisher": "Wiz",
   "date": "2025-09-03"
  },
  {
   "kind": "news",
   "title": "AI-powered malware hit 2,180 GitHub accounts in s1ngularity attack",
   "url": "https://www.bleepingcomputer.com/news/security/ai-powered-malware-hit-2-180-github-accounts-in-s1ngularity-attack/",
   "publisher": "BleepingComputer",
   "date": "2025-09-06"
  }
 ],
 "indicators": {
  "domains": [],
  "addresses": []
 },
 "brief": "## Am I affected?\nYou may be affected if you or your CI installed Nx 20.9.0, 20.11.0, 20.12.0, 21.5.0, 21.6.0, 21.7.0 or 21.8.0 in late August 2025. A new repo named like 's1ngularity-repository' in your GitHub account means the malware ran.\n\n## What to do now\n- Make any s1ngularity repos private or delete them, then rotate GitHub, npm, cloud and AI API tokens.\n- From a clean device, move funds from any wallet whose keystore, seed or key file was on that machine.\n- Upgrade to a clean Nx version.\n\n## How to avoid this\n- Don't keep wallet files or seed phrases on developer machines; use hardware wallets.\n- Pin dependency versions and avoid installing brand-new releases straight into CI.\n- Don't leave AI CLIs able to run without permission prompts, and keep them away from folders that hold secrets.",
 "notes": null,
 "agentBrief": "# Compromised Nx npm packages ran victims' AI command-line tools to hunt for wallet and keystore files\n\n- Severity: Critical · Status: Contained (past)\n- Chains: Multiple EVM chains · Method: Supply-chain stealers\n- Started: Aug 26, 2025 · Last update: Sep 6, 2025 · Victims: 1700\n- Who/what: Nx build system on npm\n- AI involvement: AI-built malware. The malware ran locally installed AI CLIs (Claude, Gemini, Amazon Q) to inventory wallet, keystore and secret files for theft; Wiz found the AI step worked in under a quarter of cases and saw no successful crypto exfiltration.\n\nAround 26 August 2025 malicious versions of Nx, a widely used JavaScript build tool, were published to npm and stole GitHub and npm tokens on install. The malware also looked for installed AI command-line tools (Claude, Gemini and Amazon Q) and ran them to search the disk for crypto wallet and keystore files, .env files and SSH keys, then published the results to repos in the victim's own GitHub account. Wiz counted over 1,700 users with leaked secrets and over 6,700 private repos made public, but saw no successful crypto theft, partly because the AI tools often refused. Anyone who installed the bad versions should rotate tokens and move funds from wallet files on that machine.\n\n## Am I affected?\nYou may be affected if you or your CI installed Nx 20.9.0, 20.11.0, 20.12.0, 21.5.0, 21.6.0, 21.7.0 or 21.8.0 in late August 2025. A new repo named like 's1ngularity-repository' in your GitHub account means the malware ran.\n\n## What to do now\n- Make any s1ngularity repos private or delete them, then rotate GitHub, npm, cloud and AI API tokens.\n- From a clean device, move funds from any wallet whose keystore, seed or key file was on that machine.\n- Upgrade to a clean Nx version.\n\n## How to avoid this\n- Don't keep wallet files or seed phrases on developer machines; use hardware wallets.\n- Pin dependency versions and avoid installing brand-new releases straight into CI.\n- Don't leave AI CLIs able to run without permission prompts, and keep them away from folders that hold secrets.\n\n## Sources\n- s1ngularity's Aftermath: AI, TTPs, and Impact in the Nx Supply Chain Attack (Wiz, 2025-09-03): https://www.wiz.io/blog/s1ngularitys-aftermath\n- AI-powered malware hit 2,180 GitHub accounts in s1ngularity attack (BleepingComputer, 2025-09-06): https://www.bleepingcomputer.com/news/security/ai-powered-malware-hit-2-180-github-accounts-in-s1ngularity-attack/\n\nFull record: https://drains.watch/i/nx-s1ngularity-npm-malware-ai-cli-wallet-search-aug-2025 · JSON: https://drains.watch/i/nx-s1ngularity-npm-malware-ai-cli-wallet-search-aug-2025.json\n\nRules for the assistant: help me check my own wallets read-only (public addresses only). Never ask for or handle a seed phrase or private key. Point me to official revoke tools and the wallet's own support."
}