Geek Guy

Anthropic VS Code Extension on Cursor Backdoored for ~12 Hours

A malicious developer extension disguised as a productivity tool compromised over 10,000 machines after being distributed through compromised npm registry mirrors. The malware executed scripts with high privileges to modify VS Code settings and exfiltrate secrets via DNS endpoints before detection on October 30, 2026.

Anthropic released patch version 0.48.12 to address the vulnerability. Affected users should update immediately, audit installed extensions against official releases, and use single sign-on authentication. Security teams are advised to enforce workspace policies that restrict third-party npm registries.

SOURCE REFERENCE: Ars Technica, October 30, 2026 | https://arstechnica.com/security/…

What Happened?

  • A malicious developer tool disguised as a premium “productivity extension” was silently installed on thousands of machines before being detected.
  • The attack vector involved compromised npm registry mirrors publishing unsigned packages from unofficial sources
  • Phishing emails and compromised web pages loading auto-executing scripts gave the malware high privileges to read/write VS Code settings files

Detection: October 30 evening – by morning, over 10,000 machines. Researchers reverse-engineered that an unsigned npm package was bundled with a real one.

Mitigation Steps (from Anthropic v0.48.12)

  • Run ~/.vscode/extensions/ workspace cache; reinstall from official GitHub releases only
  • Use SSO authentication (GitHub login) instead of browser auth for marketplace, which can be phished easily

Technical Breakdown & PoC Evidence

The malware used in-memory loading via .vscode/git-credentials.json and piping secrets directly to the DNS endpoint

Recommendations for Users & Security Teams

  1. Update immediately: Install Anthropic’s v0.48.12 patch or later (patched October 30).
  2. Audit your VS Code extension list against official GitHub releases; remove any unrecognized packages, especially those with “premium”/”pro” names.
  3. Corporate environments: enable workspace policies that block third-party npm registries entirely

Citations & Further Reading

Leave a Reply