Trojanized Claude Code Add-On Exposes Credential and Copies Read-Only Data

High · The Hacker News ·

Verification: The future-dated article URL and absence of independent corroboration make the reported event unverifiable despite vendor-quote details.

Key points

  • A maliciously altered extension in Cursor's marketplace affected the Claude Code add-on.
  • An access credential was exposed and then used to copy read-only data.
  • Fireworks AI, Cursor and Anthropic are named in the incident.
  • No CVE identifiers have been assigned; the event was reported on Friday.

An unidentified adversary compromised a Claude Code add-on distributed through Cursor's extension marketplace, turning it into a weaponized package. The incident, reported on Friday, involved Fireworks AI, Cursor and Anthropic. According to the available facts, an access credential was exposed, and that credential was subsequently used to duplicate information. The affected material appears to be limited to read-only data, suggesting the intruder could view or copy records but not necessarily alter them through that access path.

The exposure matters because developer tooling sits close to source code, credentials and cloud services. A compromised extension can become a practical entry point for credential theft, and a stolen key can be reused to reach data stores or APIs without triggering obvious malware alerts. The involvement of multiple vendor names also raises supply-chain and integration questions: organizations need to determine which environments used the affected add-on and which credentials were reachable from those environments.

No CVE identifiers have been assigned, so defenders should not wait for a vulnerability-management match before acting. The incident is best treated as a credential and supply-chain compromise rather than a conventional software flaw. The read-only scope may reduce some risk, but copied data can still create privacy, contractual and regulatory consequences, especially in a K-12 or government context where student and staff information requires strict handling.

What to watch: whether the compromised extension was pulled or patched, whether the exposed credential was rotated, and whether copied data included sensitive records. IT teams should review extension approvals, audit access logs for unusual read activity, and confirm that keys used by developer tools are scoped and monitored. Because the attacker is unknown, containment should assume the credential may have been used beyond the first observed copying action.

What to do now

  1. Remove or disable the affected Claude Code extension from Cursor environments until its integrity is confirmed.
  2. Rotate any access credential that could have been reachable from the compromised extension, then revoke old keys.
  3. Audit read-access logs for unusual copying, export or enumeration activity around the Friday incident window.
  4. Restrict developer-tool credentials to least privilege and separate read-only keys from write or administrative access.
  5. Review Cursor marketplace extension approvals and require provenance checks before reinstalling developer add-ons.
  6. Notify data owners if copied read-only records may include student, staff or other protected information.
  7. Monitor for follow-on use of the exposed credential and document containment actions for vendor and regulatory follow-up.

Original source

The Hacker News

Original AI-assisted analysis, sources cited. Verify with the vendor advisory before acting.

← All cyber news