← Voltar ao feed
high technology

Cursor breached via Fireworks AI vendor key: agent traces leaked, trojanized Claude Code extension pushed to marketplace cache

1 fonte(s) · 1 atualização(ões) · publicado 16/11/2026 03:29 · coletado há 1 hora

Cursor disclosed in a November 13 incident update that an attacker used a vendor access key exposed by Fireworks AI to copy a read-only storage bucket shared with Fireworks. The bucket held coding agent traces, mostly from 2025, from sessions outside Privacy Mode. Some traces contained credentials that had escaped redaction. Less than 0.01% of customers had exposed API credentials, and historical traces were exposed for fewer than 0.05% of users outside Privacy Mode.

Detalhes técnicos

  • The attacker then accessed archived, non-production Cursor repositories, limited support records, email conversations, product metrics, contact details, conversation summaries and credentials submitted to support.
  • On October 29, the attacker used another stolen credential to place unauthorized copies of Anthropic's Claude Code extension into the cache serving Cursor's VS Code extension marketplace. The affected versions were Anthropic.claude-code 2.1.312 and 2.1.313.
  • Cursor says Anthropic did not publish the copies and had no product vulnerability. Open VSX never hosted the malware.
  • The tampered builds potentially reached at most 5,000 users who requested specific cached versions during an exposure window of about 11 hours.
  • Cursor says Privacy Mode data, customer repositories, production infrastructure, official app updates and release signing keys were unaffected.
  • The article gives no CVEs, IOCs or attribution. It does not describe what the malicious extension did.

Remediação

  • Cursor revoked the vendor key, removed Fireworks' dataset access and moved inference traffic elsewhere. It rotated internal credentials, rebuilt the marketplace, expanded network restrictions and strengthened secret scanning.
  • Cursor removed the builds, took the marketplace offline and worked with the hosting provider to disable the attacker's server.
  • Users who installed or updated to the affected versions during the window should follow Cursor's remediation instructions, because uninstalling alone may be insufficient.
  • Cursor considers the incident contained. The last observed attacker activity was on November 1 and was blocked. External forensic specialists are assisting.
  • No independent research was run, so this report rests on the article alone.

Linha do tempo

  1. gbhackers.com ↗ · pub. 16/11/2026 03:29 · coletado 16/11 04:00 primeiro registro

    Cursor breached via Fireworks AI vendor key: agent traces leaked, trojanized Claude Code extension pushed to marketplace cache

    ler a análise desta fonte

    Cursor disclosed in a November 13 incident update that an attacker used a vendor access key exposed by Fireworks AI to copy a read-only storage bucket shared with Fireworks. The bucket held coding agent traces, mostly from 2025, from sessions outside Privacy Mode. Some traces contained credentials that had escaped redaction. Less than 0.01% of customers had exposed API credentials, and historical traces were exposed for fewer than 0.05% of users outside Privacy Mode.

    Technical Details

    • The attacker then accessed archived, non-production Cursor repositories, limited support records, email conversations, product metrics, contact details, conversation summaries and credentials submitted to support.
    • On October 29, the attacker used another stolen credential to place unauthorized copies of Anthropic's Claude Code extension into the cache serving Cursor's VS Code extension marketplace. The affected versions were Anthropic.claude-code 2.1.312 and 2.1.313.
    • Cursor says Anthropic did not publish the copies and had no product vulnerability. Open VSX never hosted the malware.
    • The tampered builds potentially reached at most 5,000 users who requested specific cached versions during an exposure window of about 11 hours.
    • Cursor says Privacy Mode data, customer repositories, production infrastructure, official app updates and release signing keys were unaffected.
    • The article gives no CVEs, IOCs or attribution. It does not describe what the malicious extension did.

    Remediation

    • Cursor revoked the vendor key, removed Fireworks' dataset access and moved inference traffic elsewhere. It rotated internal credentials, rebuilt the marketplace, expanded network restrictions and strengthened secret scanning.
    • Cursor removed the builds, took the marketplace offline and worked with the hosting provider to disable the attacker's server.
    • Users who installed or updated to the affected versions during the window should follow Cursor's remediation instructions, because uninstalling alone may be insufficient.
    • Cursor considers the incident contained. The last observed attacker activity was on November 1 and was blocked. External forensic specialists are assisting.
    • No independent research was run, so this report rests on the article alone.