Security Breach Exposes Access Key, Compromising Claude Code Extension on Cursor Marketplace
Cursor, the developer platform that hosts extensions for AI coding assistants, confirmed that its official Claude Code extension—built on Anthropic's Claude model—was compromised after an access key was stolen in a separate breach of Fireworks AI. The stolen credential allowed attackers to modify the extension in Cursor's marketplace, inserting malicious code that could hijack user sessions and exfiltrate data.
According to a statement from Cursor, the key in question was originally issued to Fireworks AI for integration purposes. When Fireworks suffered a security incident, the same key was inadvertently exposed, giving the attacker the ability to authenticate with Cursor's extension infrastructure. "An attacker obtained an access key we had issued to Fireworks," the company said, emphasizing that the breach was not a direct attack on Cursor but a downstream effect of the Firewalls AI compromise.
The malicious version of the Claude Code extension was briefly available for download before Cursor detected irregular activity and removed it from the marketplace. Users who had installed the tainted extension may have been exposed to a trojanized version of the code, potentially allowing remote command execution or data leakage. Cursor has urged all users to uninstall the extension, reset any associated API keys, and monitor their development environments for suspicious behavior.
Security experts note that the incident underscores the risks of shared credentials across third‑party services. When an access token is reused or not promptly revoked after a partner breach, it can become a vector for attackers to pivot into other ecosystems. The episode also highlights the growing importance of supply‑chain security for AI tools, where extensions and plugins can introduce vulnerabilities that affect a broad user base.
Anthropic, the creator of the Claude model, has not been directly implicated in the breach but is reviewing its partnership protocols with Cursor. Both companies said they are working together to tighten authentication flows and implement stricter key rotation policies. The broader developer community is watching closely, as the incident may prompt platform operators to adopt more rigorous vetting and monitoring of third‑party extensions to prevent similar supply‑chain attacks in the future.
Comments (0)
Be the first to comment.
Join the discussion