Malicious Extensions Hit Cursor IDE and Claude Code on Same Day

Key points

• Attackers distributed a tampered extension to people working in Cursor's IDE.
• The Claude Code extension was part of the same-day activity.
• Exposed systems belonged to developers, not general office staff.
• No CVE was assigned, so standard patch tracking will not flag this event.

Two separate but same-day security events have put developer workstations in the spotlight. According to the available information, unknown operators spread a tampered add-on through Cursor's IDE and also touched the Claude Code extension ecosystem. The activity appears aimed at people who use Cursor for coding, and the result was exposure of their machines rather than a broad enterprise outage.

The affected population is narrow but high-value: software developers with access to source code, credentials, build systems, and internal tooling. Because these users often install plugins and extensions without waiting for central approval, a poisoned package can travel quickly from a marketplace listing to a live workstation. The two vendors named are Cursor and Anthropic; the products involved are Cursor IDE and the Claude Code extension.

No CVE identifiers were assigned in the facts provided. That matters because many security programs prioritize patchable vulnerabilities, while supply-chain tricks in developer tooling often fall outside that queue. The absence of a CVE does not make the event harmless; it changes the detection and response path toward extension inventory, endpoint telemetry, and credential hygiene.

Watch for follow-on signs: unexpected extension installs, editor processes making unfamiliar outbound connections, new tokens or SSH keys, and unusual package-publishing activity. Treat same-day reports as a prompt to verify what is installed in developer environments and to confirm whether affected users reused credentials in other systems.

What to do now

1. Inventory Cursor IDE and Claude Code extensions across developer endpoints, and remove unknown or recently added add-ons pending review.
2. Enforce extension allowlists and restrict sideloading in developer tools; require approval for marketplace installs.
3. Rotate credentials and tokens used on affected developer machines, including source control, package registry, cloud, and SSH keys.
4. Hunt endpoint telemetry for editor child processes, unusual outbound connections, and extension install events tied to the same-day timeframe.
5. Review developer workstation logs for persistence, new scheduled tasks, startup items, and tampered editor configuration.
6. Warn developers not to install extensions from unsolicited links or unofficial listings, and verify publisher identity before installation.
7. Add extension supply-chain incidents to the response playbook and monitor advisories from Cursor and Anthropic because no CVE is available.

Original source

Dark Reading