Nx Console 18.95.0 for VS Code ran a credential stealer when the extension started, for users who updated on 18 May 2026.
The Nx command line tool, the @nx/* plugins and Nx Cloud were not affected. Only the extension was.
What happened
Attackers published a poisoned Nx Console 18.95.0 to the Visual Studio Marketplace and to Open VSX on 18 May 2026.
- An Nx contributor ran
pnpm installin another repository on 11 May 2026. It pulled a malicious@tanstack/zod-adapterrelease. - The malware read the GitHub CLI token from
~/.config/gh/hosts.yml. The attacker used it until 16 May 2026. - On startup the extension ran one shell command, disguised as an MCP setup task. It downloaded and ran a hidden package from a planted commit in
nrwl/nx. - The stealer targeted Vault, npm, AWS, GitHub, GCP and Kubernetes tokens, 1Password sessions, SSH keys,
.envfiles and Docker configuration. - It sent data over HTTPS, the GitHub API and DNS.
The upload reached the Visual Studio Marketplace at 12:30 UTC. Removal came at 12:47 UTC there and 13:09 UTC on Open VSX. The Hacker News attributes the attack to TeamPCP.
Affected versions
- Nx Console (VS Code extension) 18.95.0 only.
- Patched in 18.100.0 and later.
- Exposure window: 18 May 2026, 12:30 to 13:09 UTC.
- Not affected: the
nxnpm package, the@nx/*plugins and Nx Cloud. - The GitHub advisory is GHSA-c9j4-9m59-847w. It lists CVE-2026-48027 with critical severity.
Indicators of compromise
- macOS and Linux:
~/.local/share/kitty/cat.py,/tmp/kitty-*and/var/tmp/.gh_update_state. - macOS:
~/Library/LaunchAgents/com.user.kitty-monitor.plist. - Windows:
%USERPROFILE%\.local\share\kitty\cat.py,%TEMP%\kitty-*,%TEMP%\.gh_update_stateand%USERPROFILE%\.bun\bin\bun.exe. - A Python process that runs
cat.py. - Any process with the environment variable
__DAEMONIZED=1. - On Linux, unexpected entries in
/etc/sudoers.
How to check
List your installed extension versions and look for 18.95.0. Then look for the dropped files. Missing files give an error, which is a good result.
code --list-extensions --show-versions | grep angular-console ls -l ~/.local/share/kitty/cat.py /var/tmp/.gh_update_state ~/Library/LaunchAgents/com.user.kitty-monitor.plist
What to do now
- Update Nx Console to 18.100.0 or later.
- Stop any process that runs
cat.pyor carries__DAEMONIZED=1. On macOS, unload the LaunchAgent first, then remove the files. - Rotate every credential that was on disk or reachable through
op,gcloud,aws stsorghduring the window. Check/etc/sudoerson Linux. - Treat a machine that ran 18.95.0 as compromised. The postmortem suggests a full rebuild after you rotate credentials.
Frequently asked questions
How long was the malicious version available?
The Nx postmortem shows about 11 minutes on the Visual Studio Marketplace and about 36 minutes on Open VSX. The GitHub advisory says about 18 minutes on Microsoft's platform.
How many users installed it?
The postmortem counts 28 installs from the Visual Studio Marketplace and 41 downloads from Open VSX. Its activation data shows about 6,000.
Was the Nx npm package affected?
No. Only the VS Code extension was.
Sources
Send this page to the person who looks after AI at your company.