An update on our recent security incident
Cursor says exposed historical agent traces led to credential theft and a tampered Claude Code extension in its cached marketplace. Teams should check the affected versions and rotate any exposed keys.
Cursor says an access key exposed at Fireworks let an attacker copy historical traces from a shared bucket; some traces contained unredacted credentials. The attacker used a credential from Cursor’s systems to serve tampered Claude Code extension versions **2.1.312 and 2.1.313** through Cursor’s cached marketplace for about **11 hours** on October 29; up to 5,000 users requesting those versions may have received them.
If your team installed or updated to either version from Cursor’s marketplace during that window, follow Cursor’s security notice steps; uninstalling alone may not be enough. Rotate any exposed credentials and check whether affected team admins were contacted.
Cursor says an access key exposed at Fireworks let an attacker copy historical traces from a shared bucket; some traces contained unredacted credentials. The attacker used a credential from Cursor’s systems to serve tampered Claude Code extension versions **2.1.312 and 2.1.313** through Cursor’s cached marketplace for about **11 hours** on October 29; up to 5,000 users requesting those versions may have received them. If your team installed or updated to either version from Cursor’s marketplace during that window, follow Cursor’s security notice steps; uninstalling alone may not be enough. Rotate any exposed credentials and check whether affected team admins were contacted. Cursor says fewer than 0.01% of customers had API credentials exposed and fewer than 0.05% of non-Privacy-Mode users had traces exposed; it says affected users were notified. The notice says the incident is contained, but monitoring continues.
This update broadens the earlier malicious-extension notice into an incident account: it traces the exposure to a leaked access key and copied historical traces, specifies the affected versions and an approximately 11-hour window, and reports limited credential exposure. It also reinforces that uninstalling alone may not remediate affected machines; Cursor says the incident is contained while monitoring continues.