November 14, 2026 · Follow-up to the November 13 vendor update
Cursor's November 13 account links exposed historical AI traces, stolen credentials and its October 29 extension-cache attack. At most 5,000 users potentially received malware; infections are not confirmed at that scale. Cursor says neither Anthropic nor Open VSX supplied the malicious package. These are vendor findings, not our forensic conclusions.
Three exposure questions, not one
For IT teams, the useful distinction is between data already copied, credentials that still grant access, and software running on a workstation. Each needs a separate response record. Closing one does not automatically close the others.
- Historical data: review the account-specific notice and identify the information involved. Replacing a key cannot retrieve a copied trace.
- Credential access: assign an owner to each identified credential, track its issuer and dependent services, and document replacement and revocation separately. Keep secret values out of incident tickets.
- Endpoint integrity: establish which package was installed, from which marketplace and when. A product name alone does not establish distribution provenance.
Use the affected package and time window
Cursor's remediation notice identifies macOS and Windows packages Anthropic.claude-code 2.1.312 and 2.1.313 distributed through its VS Code marketplace between about 2:27 a.m. and 1:35 p.m. Pacific on October 29. It warns that uninstalling may leave persistence behind. It calls for telemetry review, isolation where payload execution or backdoor installation is evident, and credential rotation from a trusted system.
Use the vendor's current indicators and remediation guidance with your incident-response team. This article deliberately does not reproduce scripts or treat a single negative indicator check as proof that a device is clean.
Privacy Mode answers a narrower question
Cursor excludes Privacy Mode prompts and code from the historical-trace exposure. That is not an exemption from checking a downloaded extension. Likewise, its statement that the incident is contained is a vendor assessment, not proof about a particular workstation.
No customer account or device was inspected for this article. Check account-specific notifications and the latest primary notices before acting.