ChainCatcher report: Cursor has released an update on the recent security incident. After two weeks of a comprehensive investigation, it was determined that the breach originated when an attacker obtained an access key issued by Cursor to Fireworks. This key was subsequently leaked by Fireworks, allowing the attacker to replicate limited tracing data for programming agents and further compromise certain SaaS tools, gaining access to archived source code, support data, and other information. The attacker then used the stolen credentials to distribute a malicious copy of the Anthropic Claude Code extension (versions 2.1.312 and 2.1.313) in the Cursor VS Code extension marketplace cache on October 29. Up to approximately 5,000 users may have been affected; the malicious version was removed after about 11 hours. Cursor emphasized that the vast majority of customers were not impacted, and affected customers have been notified directly. Data for users in privacy mode remains secure; production systems, official application updates, and customer code repositories were not compromised. The company has rotated credentials, migrated inference traffic, and rebuilt the extension marketplace, and believes the incident was contained as of November 1.
Cursor Updates Security Incident: Most Users Unaffected, 5,000 Possibly Impacted
ChaincatcherShare
Cursor disclosed a security breach following a two-week investigation, revealing that attackers obtained a leaked access key from Fireworks, which allowed them to replicate trace data and infiltrate SaaS tools, gaining access to source code and support data. On October 29, a malicious Anthropic Claude Code extension (versions 2.1.312 and 2.1.313) was distributed through the Cursor VS Code marketplace, potentially affecting 5,000 users. The malicious versions were removed after 11 hours. Cursor confirmed that most users were not impacted, and affected users were notified directly. Production systems and user data remain secure. The company rotated credentials, rebuilt the marketplace, and contained the incident by November 1. This incident occurs amid ongoing updates to the platform’s security measures.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.