Review extension releases
Use approved extensions, validate release provenance and consider a waiting period for new versions.
What this does—and does not—establish
A trusted name cannot establish that a marketplace copy is authentic.
Cursor reports altered Claude Code extensions distributed through its marketplace.
Source: CursorThe distribution window was about 2:27 a.m.–1:35 p.m. Pacific time. Earlier attacker access is undated.
Cursor’s marketplace distributed an extension carrying hidden malicious code.
CursorLoading the extension triggered collection of computer details and attempts to establish remote access.
Microsoft Security ResearchStartup changes could keep it running. Errors and permission requirements could block remote access while leaving harmful files behind.
Microsoft Security ResearchEditorial analogy: a familiar delivery contains a spare door key planted by someone else. Taking back the delivery does not recover a spare key left behind.
An analogy for the mechanism; not an additional claim about the incident.Cursor identifies versions 2.1.312 and 2.1.313 for macOS and Windows. Cursor
Microsoft found code intended to enable persistent remote access. Microsoft Security Research
Cursor says errors and missing administrator privileges blocked remote access on most Macs and Windows PCs. Total affected users and successful logins remain unknown.
AI tooling was targeted; AI assistance in creating the attack is unproven.
Microsoft says Anthropic’s systems, Visual Studio Marketplace and the official npm distribution were unaffected.
Collected setting names did not contain the secret values stored under those names.
Editorial lesson: software around an AI assistant needs its own security checks. Investigate what an altered add-on changed, not just whether it is still installed.
Someone altered the extension; attribution remains unknown. Cursor
Cursor says it removed the releases, rebuilt its marketplace and took the attacker’s server offline. Cursor
Editorial defense mapping for organizations adopting coding assistants. It does not establish missing controls or guarantee prevention.
Use approved extensions, validate release provenance and consider a waiting period for new versions.
A trusted name cannot establish that a marketplace copy is authentic.
Keep routine coding work separate from administrator access and sensitive credentials.
Some malicious changes can occur without administrator rights.
Check device activity, unauthorized access and startup changes; preserve evidence before cleanup.
Removing an extension or disabling an attacker server does not establish that a device is clean.
Editorial connections to relevant controls, not evidence that a particular technology would have prevented this case. Each guide links to the security guidance behind its recommendations.
Explore the full AI security frameworkExplore more original accounts in the source report library ↗.
These are source-reported findings. An independent assessment, when available, is labeled explicitly.
01Read this case’s update history →
Reviewed Oct 31, 2026 · Editorial methodology · Structured data