TabSphere journal / Software development
Backdoored Claude Code extension on Cursor, what small businesses should know
A tampered copy of the Anthropic 'Claude Code' VS Code extension was briefly distributed via the Cursor marketplace and attempted to install a persistent SSH backdoor. Up to about 5,000 users may have installed or auto‑m

This story is developing and details may change. Last checked 2 Nov 2026.
What happened
Reported by Inside a malicious Claude Code-branded extension and its persistent SSH backdoor, Microsoft Security Blog on 30 Oct 2026. The event itself dates from 29 Oct 2026.
A modified copy of the Anthropic 'Claude Code' VS Code extension (anthropic.claude-code) was published on the Cursor VS Code Extension Marketplace for about 11, 12 hours on 2026‑10‑29. The tampered package carried version identifiers reported as 2.1.313 (with 2.1.312 also implicated) and attempted to install a persistent SSH backdoor by adding an attacker-controlled SSH key, enabling local SSH services or platform mechanisms, and opening a reverse SSH tunnel to permit remote access. Microsoft’s analysis indicates the compromise was limited to the Cursor marketplace and that other distribution channels for the extension were not affected. Community detection tools and scanners were quickly published with indicators of compromise to help find affected installs. 1 2 3 4 5
Why it matters to small businesses
If you or someone on your team uses VS Code extensions from alternative marketplaces, there is a real risk that a tampered extension can execute code on developer machines. The malicious package tried to create persistent remote access and could expose secrets or files if its payload ran. Cursor estimates up to about 5,000 users may have been exposed during the distribution window. On some platforms full persistence reportedly required elevated privileges and so did not always succeed, but the payload could still leak data where it executed. Community scanners exist to check for known indicators of compromise. 2 1 3 4 5
TabSphere's view
This section is TabSphere's interpretation, not reported fact.
Interpretation: The incident is a reminder that developer tools and third‑party marketplaces are potential supply‑chain weak points. Small teams should treat developer machines and the extensions they run as part of their wider software estate. Keep trusted sources, limit what runs with elevated rights, and have practical steps to check and recover if a compromised package is suspected.
What to do next
- Check whether your team installed the extension. Ask developers whether they installed or auto‑updated the Claude Code extension from Cursor during the incident window. If unsure, check extension lists on developer machines and compare versions against the implicated numbers in the report.
- Search for published indicators and run scanners. Use the community detection tools and repositories that were published to look for known file names, hashes and other indicators of compromise. Prioritise machines used for development or that hold credentials and secrets.
- Rotate affected keys and credentials promptly. If you find signs the backdoor ran or you are uncertain, rotate SSH keys, API keys and other credentials that might be exposed. Replace keys used on developer machines and any systems those machines access.
- Limit developer privileges and isolate builds. Where practical, avoid running developer tools with administrative privileges. Use isolated build or test environments for code that touches production systems or secrets, and keep backups of critical configuration and code.
Sensible precautions
- Treat community scanners as helpful but not exhaustive; follow vendor guidance where available.
- If a machine shows indicators and you lack expertise, avoid using it for sensitive work until it is cleaned or rebuilt.
- Do not assume other extension marketplaces or official vendor infrastructure were affected unless an authoritative source says so.
What isn't known yet
- Reported exposure is an estimate from the Cursor marketplace and may not precisely reflect all affected installs.
- Reports indicate full persistence often required elevated privileges on some platforms, so impact may vary by machine configuration.
This kind of supply‑chain tamper is unsettling, but it is manageable with calm, practical steps. Confirm what was installed, use available indicators to check machines, and replace any exposed keys. Small teams that standardise sources, limit privileges and keep simple recovery plans will reduce the chance of an incident causing lasting disruption.
If you want to talk through how your website, software or design setup can reduce risk from toolchain incidents, get in touch for a practical conversation.
Sources
Checked 2 Nov 2026.
- Anthropic VS code extension on Cursor backdoored for nearly 12 hours, Ars Technica (published 30 Oct 2026)
- Inside a malicious Claude Code-branded extension and its persistent SSH backdoor, Microsoft Security Blog (published 30 Oct 2026)
- Malicious Claude Code extension on Cursor planted SSH backdoors, BleepingComputer (published 30 Oct 2026)
- GitHub, check-claude-code-exfil (indicators/scanner) (published 30 Oct 2026)
- GitHub, claude-code-backdoor-check (read-only scanner) (published 30 Oct 2026)
