Blog

Malicious Claude Code extension: cleanup beyond uninstalling

Use Cursor’s October 29 incident notice to study affected-package scope, persistence and evidence-based recovery for Security+ SY0-701.

· 3 min read

Removing a malicious application and recovering from an incident are not necessarily the same task. Cursor's October 29 notice, updated October 30, identifies malicious macOS and Windows packages of the Anthropic.claude-code extension, versions 2.1.312 and 2.1.313, distributed through the Cursor VS Code Extension Marketplace. The notice says the payload could leave standalone background scripts after the extension was removed. That makes the case useful for learning why incident response follows the effects of execution, not just the name of the installed program. Read Cursor's incident notice and current recovery instructions.

Identify the affected distribution before drawing conclusions

Cursor names installations or updates from its marketplace between about 2:27 a.m. and 1:35 p.m. Pacific time on October 29, 2026. It says these malicious versions were not developed by Anthropic and that it has no evidence other versions or the official distribution were affected. Keep the marketplace, version, operating system and installation window together in your notes. A familiar publisher name is not enough to identify which package was actually installed. Those scope limits come from the vendor's notice, not a claim that every Claude Code installation was compromised.

Follow what the payload tried to leave behind

According to Cursor, the extension collected host and user details, attempted to add an attacker-controlled key for Secure Shell (SSH), and attempted to enable the local SSH service and open a reverse tunnel. SSH provides remote access; the reverse tunnel was intended to create a connection back toward the attacker. Background persistence used a LaunchAgent on macOS or a scheduled task with a startup-script fallback on Windows. Persistence means a mechanism that can keep running or return without launching the original application. Cursor lists the payload behavior and indicators of compromise.

The notice also limits what can be concluded: enabling the local SSH service required administrator rights the extension generally lacked, and errors meant that step would normally fail unless Cursor had been started with elevated privileges. Cursor says the attacker server has been taken offline. Neither caveat removes its cleanup advice. Do not turn an attempted access mechanism into a claim that every affected user suffered a successful remote takeover.

Connect the case to Security+ rather than memorizing filenames

The official CompTIA Security+ V7 summary for SY0-701 covers supply-chain and vulnerable-software attack vectors, incident response, investigation data sources and vulnerability remediation and validation. This case lets you practice those distinctions using a specific vendor report. Use the Nex Arc SY0-701 study guide for the surrounding concepts, then ask which evidence in this incident would justify each response.

For a study exercise, make three columns: evidence, action and reason. Put the extension-installation record in the first column and use it to determine whether the affected package was present. Put an unauthorized SSH key or a background task in a separate row. Explain why deleting the extension does not, by itself, demonstrate that the separately recorded artifact is gone. This is an exercise in tracing evidence, not an instruction to run a malicious sample.

Distinguish containment, cleanup and credential recovery

Cursor recommends inspecting endpoint, network and installation records, isolating hosts with evidence of payload execution or backdoor installation, removing unauthorized keys and persistence, stopping tunnel processes and considering whether the host needs rebuilding. It also advises rotating accessible credentials and sessions from a trusted system. Uninstalling alone may be insufficient because the background scripts are separate from the extension. The notice supplies platform-specific remediation scripts and their intended execution context.

For an actual affected machine, follow those current vendor instructions and your organization's incident procedure rather than treating this article as a replacement runbook. For exam preparation, the useful question is narrower: what evidence would show that each unwanted access path has been addressed? An application disappearing from the extensions list answers only the application-removal part of that question.

Read the SY0-701 study guide

Sources