Supply Chain Breach: How Stolen Vendor Keys Compromised Cursor's Ecosystem

Cursor, the AI-powered code editor, has revealed new details about a recent security incident. The attack didn't target Cursor's infrastructure directly—instead, hackers exploited access keys leaked from their vendor, Fireworks.

The Attack Path: From Vendor Keys to Marketplace

According to the disclosure, attackers used credentials obtained from the vendor breach to access some of Cursor's internal tools. On October 29, they uploaded a modified version of the Claude Code extension into Cursor's extension marketplace cache.

The malicious version remained available for approximately 11 hours before being identified and removed. During that window, up to 5,000 users may have been exposed to the compromised extension.

Scope and Response

Cursor emphasized that the actual impact was limited: fewer than 0.01% of customers had API credentials exposed. The company has directly notified all affected users and provided guidance on securing their accounts.

  • Attack leveraged third-party vendor access, not a direct system breach
  • Malicious extension circulated for nearly half a day before detection
  • While the percentage is small, the potential user impact remains significant

Cursor states the incident is now contained, with relevant vulnerabilities patched. The company is strengthening its vendor key management protocols to prevent similar breaches.

This event underscores a growing challenge in software development: supply chain security. Even tools like Cursor, built for developer productivity, face risks through third-party dependencies.