[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fA2osOv0Tl8NPcOs92QoTVcmZ6FDC0YP9E0BAK82qTgE":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"55aafe48-147a-46a5-adc8-79be3d93b839","stolen-credentials-at-ai-provider-enable-malicious-extension-distribution","8df3881e-7a08-4010-8242-41bacfc26a1b","Stolen Credentials at AI Provider Enable Malicious Extension Distribution","Attackers compromised Cursor's marketplace by first stealing credentials from a third-party AI infrastructure provider, Fireworks AI, illustrating how a supplier's weak credential security becomes a direct attack vector against downstream customers. Once inside Cursor's internal systems, the attackers weaponized the trust developers place in marketplace extensions to distribute a backdoored version of the Claude Code extension. The malicious extension was live for approximately 11 hours before detection, during which it attempted to install persistent SSH backdoors on developer workstations. This incident underscores that an organization's security posture is only as strong as its least-secure supplier's credential hygiene.","**Immediate actions:**\n- Rotate all credentials and API keys shared with or issued to third-party providers following any suspected supplier compromise.\n- Audit the integrity of all marketplace-hosted extensions and enforce cryptographic signing to detect unauthorized modifications.\n- Revoke or suspend compromised extensions immediately and notify affected users with specific remediation steps.\n\n**Long-term improvements:**\n- Require MFA and least-privilege access for all third-party vendors and service accounts that have any access to internal systems or distribution pipelines.\n- Implement a formal supplier security assessment program that evaluates credential management and access controls before onboarding providers.\n- Enforce code-signing and provenance verification for all extensions published to your marketplace so tampering is detectable before distribution.\n\n**Detection measures:**\n- Deploy behavioral monitoring on developer endpoints to detect unexpected outbound SSH connections or new authorized_keys entries indicative of backdoor installation.\n- Set up real-time alerting on extension publish or update events in the marketplace, requiring human approval for any changes to high-trust packages.\n- Establish continuous monitoring of third-party provider access logs to detect anomalous credential use early in the attack chain.",[12,13,14,15,16],"NIS2 Article 21(2)(d)","NIS2 Article 21(2)(j)","NIST SP 800-53 SA-12: Supply Chain Protection","CIS Control 16: Application Software Security","MITRE ATT&CK T1195.002: Compromise Software Supply Chain",{"NIS2 Article 21(2)(d)":18,"NIS2 Article 21(2)(j)":19,"CIS Control 16: Application Software Security":20,"NIST SP 800-53 SA-12: Supply Chain Protection":21,"MITRE ATT&CK T1195.002: Compromise Software Supply Chain":22},"This point requires organizations to manage security risks in their supply chain, which would have mandated assessing Fireworks AI's credential security before granting it access to Cursor's internal systems.","This point requires multi-factor authentication and secured communications, which—if enforced for Fireworks AI's access—would have prevented stolen credentials alone from being sufficient to breach Cursor's systems.","CIS Control 16 requires securing software supply chains including integrity verification of third-party components, which—if applied to marketplace extensions—would have detected or prevented the distribution of the tampered Claude Code extension.","SA-12 requires organizations to apply security controls to protect against supply chain threats, directly covering the risk of a compromised third-party provider being used as a stepping stone into internal systems.","This technique describes adversaries tampering with software before delivery to end users, which precisely matches the attackers' method of pushing a malicious extension through Cursor's legitimate marketplace.","published","2026-11-14T18:20:23.847697+00:00","2026-11-14T18:20:23.817+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fcursor-confirms-security-breach-led-to-malicious-claude-code-extension\u002F","cursor-confirms-security-breach-led-to-malicious-claude-code-extension-2396f4","Cursor confirms security breach led to malicious Claude Code extension",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"1ec88fde-2d0f-4ed8-932a-33f5ccc0fdc7","Access Control","access-control","Excessive privileges, missing MFA, weak auth","#f97316",{"id":38,"name":39,"slug":40,"description":41,"color":42},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"aa1c403b-5c3c-4cfa-8a85-dc5b0ba6eb4e","2026-11-15","morning","ThreatNoir Weekend Brief — November 15","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-15\u002Fthreatnoir-morning-brief-2026-11-15.mp3",[51,55,59],{"slug":52,"name":53,"problem":54},"identity-governance","Identity governance and single sign-on","People who leave or change roles lose access everywhere at once, and forgotten accounts stop piling up.",{"slug":56,"name":57,"problem":58},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",{"slug":60,"name":61,"problem":62},"third-party-risk-management","Third-party risk management (TPRM)","You know which suppliers could hurt you, and you hear quickly when one of them is breached."]