[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fPKIdQxZ5f-o9eyRGsmotX6wd_nEHSiGLghjEdZe5f4c":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":19,"status":27,"created_at":28,"published_at":29,"article":30,"tags":34,"podcasts":47,"controls":48},"56ab3981-eb1e-4d4d-8d7f-88763455314c","malicious-cursor-marketplace-extension-backdoors-up-to-5000-developer-systems","e1186e8e-c852-4ffc-9a76-7d673a1b5e6e","Malicious Cursor Marketplace Extension Backdoors Up to 5,000 Developer Systems","A trojanized Claude Code extension (v2.1.313) was distributed through Cursor's marketplace, embedding SSH key injection, reverse tunnel establishment, and persistence mechanisms — classic supply chain attack hallmarks targeting developer tooling. The incident exposes how extension marketplaces can become high-value attack vectors when publisher identity verification and code vetting are insufficient. Developers inherently trust marketplace listings, making malicious packages particularly dangerous as they execute with user-level or elevated permissions. The discrepancy between Cursor's marketplace records and Open VSX\u002Fnpm registries also highlights a monitoring gap that delayed detection and complicated attribution.","**Immediate actions:**\n- Audit and remove any installed instances of Claude Code extension v2.1.313 and rotate SSH authorized_keys files on all affected developer machines.\n- Scan systems for unauthorized SSH keys, active reverse tunnel processes, and persistence artifacts (cron jobs, systemd units, startup scripts) introduced by the extension.\n\n**Long-term improvements:**\n- Require cryptographic signing and automated static analysis of all extensions before marketplace publication, including checks for network calls, file system writes, and shell execution.\n- Establish a cross-registry validation process to reconcile package publication records across all distribution channels (npm, Open VSX, proprietary marketplaces) and flag discrepancies automatically.\n- Implement least-privilege sandboxing for IDE extensions to restrict their ability to modify SSH configurations or establish outbound tunnels.\n\n**Detection measures:**\n- Deploy endpoint monitoring rules to alert on unauthorized modifications to `~\u002F.ssh\u002Fauthorized_keys` and unexpected outbound SSH connections from developer workstations.\n- Maintain a software bill of materials (SBOM) for all installed extensions and tooling, enabling rapid impact assessment when a malicious package is identified.",[12,13,14,15,16,17,18],"CIS Control 7: Continuous Vulnerability Management","OWASP A06:2021 Vulnerable and Outdated Components","NIST SP 800-53 SI-2: Flaw Remediation","MITRE ATT&CK T1566: Phishing","CIS Control 17: Incident Response Management","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","NIS2 Article 21(2)(b)",{"NIS2 Article 21(2)(b)":20,"MITRE ATT&CK T1566: Phishing":21,"NIST SP 800-53 SI-2: Flaw Remediation":22,"CIS Control 17: Incident Response Management":23,"OWASP A06:2021 Vulnerable and Outdated Components":24,"CIS Control 7: Continuous Vulnerability Management":25,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":26},"NIS2 mandates supply chain security measures including assessment of third-party software integrity, which would require marketplace operators like Cursor to implement publisher verification and code review controls.","Distributing a trojanized package through a trusted marketplace mirrors phishing logic — abusing an inherently trusted channel — and ATT&CK's supply chain compromise techniques (T1195) map directly to this delivery method.","SI-2 requires organizations to identify and remediate flawed or malicious software components promptly, which would mandate rapid detection and removal processes for compromised marketplace extensions.","The confusion around distribution channels and delayed attribution underscores the need for a tested incident response plan that includes supply chain compromise scenarios and cross-platform registry reconciliation steps.","This attack exploited blind trust in marketplace-distributed components; vetting third-party extensions for malicious code is exactly the risk A06 addresses in software supply chains.","Regular automated scanning of installed software — including IDE extensions — against known-malicious package signatures would have flagged version 2.1.313 before widespread installation.","A.8.8 requires organizations to track and respond to vulnerabilities in software they operate or distribute, directly applicable to marketplace operators vetting extensions before publication.","published","2026-10-30T11:21:29.114825+00:00","2026-10-30T11:21:29.064+00:00",{"id":7,"url":31,"slug":32,"title":33},"https:\u002F\u002Fsocket.dev\u002Fblog\u002Fclaude-code-extension-compromise?utm_medium=feed","cursor-removes-malicious-claude-code-2-1-313-extension-from-its-marketplace-4fb089","Cursor Removes Malicious Claude Code 2.1.313 Extension From Its Marketplace",[35,41],{"id":36,"name":37,"slug":38,"description":39,"color":40},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":42,"name":43,"slug":44,"description":45,"color":46},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[],[49,53,57],{"slug":50,"name":51,"problem":52},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",{"slug":54,"name":55,"problem":56},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them.",{"slug":58,"name":59,"problem":60},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship."]