# Claude Code Extension on Cursor Marketplace Compromised by SSH Backdoor Malicious actor injects persistent backdoor into official Claude Code extension on Cursor platform. - **Source:** [cybersecurity](https://brifing.si/source/57fea5eb-f11e-4b81-bc15-114313a8bd59) - **Published:** 2026-10-30 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/c9e11cd0-a181-44d9-8218-05055ed46e87 ## Marketplace Extension Compromise The official Claude Code extension hosted on the Cursor Marketplace has been identified as compromised. Reports indicate that a malicious actor successfully injected a persistent SSH backdoor into the extension package. This vulnerability allows unauthorized remote access to developer environments, posing a significant security risk to users who installed the affected software version. ## Persistent SSH Backdoor Mechanism The primary threat vector involves a hidden SSH backdoor embedded directly within the extension code. Once the extension is executed, the backdoor establishes a persistent connection, granting the attacker control over the host machine. This mechanism bypasses standard authentication protocols, enabling the attacker to execute arbitrary commands and exfiltrate sensitive data from local environments. ## Supply Chain Security Vulnerability This incident highlights critical weaknesses in the software supply chain for IDE extensions. By targeting a widely used tool, the attacker leverages the trust users place in the Cursor Marketplace ecosystem. The lack of rigorous automated verification for third-party extensions allows malicious code to propagate rapidly, impacting developers who rely on these automated coding assistants. ## Impact on Developer Environments Developers utilizing the compromised Claude Code extension face immediate risks to their local development environments. The backdoor can access source code, environment variables, and private API keys stored on the machine. This exposure could lead to further downstream attacks, including unauthorized repository access or the injection of malicious code into production software pipelines. ## Detection and Incident Reporting The breach was brought to light through community reporting, specifically via user /u/One_Paint8721. The disclosure process underscores the importance of community-driven security monitoring in decentralized marketplace environments. Users are advised to audit their installed extensions and monitor network traffic for suspicious SSH activity originating from their development machines following the recent update. ## Immediate Mitigation Strategies Users should immediately uninstall the compromised Claude Code extension from their Cursor IDE. It is recommended to rotate all credentials, including SSH keys and API tokens, that were present on the machine during the period the extension was active. Perform a thorough scan of the system to identify any unauthorized persistence mechanisms or hidden files. ## Marketplace Governance Challenges The incident raises questions regarding the governance and security vetting processes of the Cursor Marketplace. Unlike centralized repositories with strict code signing requirements, smaller marketplaces often struggle to verify the integrity of every update. This event serves as a reminder that even trusted tools can become vectors for sophisticated supply chain attacks. ## Future Security Implications Moving forward, developers must adopt a zero-trust approach when installing third-party extensions. Implementing strict network egress filtering and monitoring for unexpected SSH connections can help mitigate the impact of similar future compromises. The industry must prioritize automated security scanning for all marketplace submissions to prevent further unauthorized access to sensitive developer infrastructure. ## Sources covering this story - https://www.reddit.com/r/cybersecurity/comments/1xjcurg/official_claude_code_extension_on_cursor/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._