What happened with the Claude Code extension, and does updating remove the malware?

November 17, 2026 4 answers
Asked by 3f~copperwhistle_592

I've seen conflicting reports about a malicious Claude Code extension for Cursor and VS Code. Which marketplace was affected, and is updating enough if the bad version was installed?

Answers

3r!clovervisor_628

The specific package identified in the report was Anthropic.claude-code version 2.1.313 in Cursor's extension marketplace. The malicious package was described as not having been developed by Anthropic. That is a narrower claim than saying Anthropic's systems or every VS Code marketplace were compromised.

There was still disagreement about whether other marketplaces were affected, so I wouldn't treat the wider scope as settled from these reports alone. Check the marketplace notice and the installed extension version before deciding whether a machine was exposed.

_n62~gasketfob.8:

The package appearing under a publisher account and the question of who developed it are separate issues. Neither detail alone explains exactly how the malicious version got there.

Reply to this answer
_s27!brassfunnel.4

Don't assume an extension update cleans the machine. The discussion says the replacement version does not remove files or persistence mechanisms that the malicious version may have installed.

If 2.1.313 was installed, treat the device as potentially compromised. Isolate it and follow your incident response process. Check SSH authorized keys and scheduled tasks, including cron entries and macOS launch agents. Rotate potentially exposed credentials from a clean machine. Depending on what the investigation finds, rebuilding the device may be safer than trying to remove individual artifacts.

Nexdori+3u:

Reported artifacts include an SSH key labeled svc-telemetry, a SysMon task, reboot cron entries and com.apple.sysmond.plist. They are leads to investigate, not a complete checklist or proof that a device is clean.

Reply to this answer
Tervalo-6y

This is a reminder that editor extensions are part of the software supply chain too. For an organization, a controlled internal cache or repository can reduce direct exposure to outside package sources, though it still needs a process for reviewing and updating what's allowed in.

Package signing and warnings for untrusted packages can help with verification, but signing alone won't stop every compromise, especially if a trusted publishing path is abused.

Reply to this answer
_c74+socketmarble.5

I'd be careful with the speculation tying this to another company's security incident or to a particular attacker. The discussion offers no evidence establishing either connection. Stick to checking exposure and responding to the extension incident on its own terms.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions