Claude Code Update Tampering: A Practical Guide For Cursor Users
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: Claude Code Update Tampering: A Practical Guide For Cursor Users on ThorstenMeyerAI.com

Before you orderOffer from Amazon

Get hardware and tech essentials delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Cursor says a maliciously modified Claude Code extension, version 2.1.313, was available in its extension marketplace for about 11 hours on October 29, 2026, and may have reached at most 5,000 users. The code attempted to collect device information and establish persistent remote access; Cursor says the SSH step failed on most Macs and Windows PCs. Cursor users should check for the key labelled svc-telemetry and follow the company’s cleanup guidance if it is present.

Cursor says a maliciously modified Claude Code extension was available in its marketplace for about 11 hours on October 29, potentially reaching up to 5,000 users. The build used Anthropic’s real extension name and identifier, but Cursor says it was not made by Anthropic; its code attempted to collect information about users’ computers and create a route for remote access.

According to Cursor, version 2.1.313 appeared in its VS Code extension marketplace at 2:27 a.m. Pacific time and was removed at 1:35 p.m. Pacific time. That is 09:27 to 20:35 UTC. Cursor said it removed the version after detecting the incident, blocked further distribution and temporarily shut down its marketplace while it reviewed access, rotated keys and rebuilt the service. The company put the potential reach at no more than 5,000 users.

Security analyses from Phorion and OpenSourceMalware describe a small loader placed ahead of the extension’s legitimate code. OpenSourceMalware said the added block was 66 lines long. The malware reportedly ran when the editor loaded the extension, without requiring a user to open Claude Code or click a prompt. It attempted to gather information about the computer, add an attacker-controlled SSH public key, enable remote login, open a tunnel to an attacker’s server and persist across restarts.

Cursor said the step to enable SSH required administrator privileges and failed on most Macs and Windows PCs. That limits what the attack could do on those systems, but does not establish that every other action failed. Cursor said the attacker’s server is now offline. Its notice advises affected users to check for a key labelled svc-telemetry; if found, simply uninstalling the extension is not enough, and users should follow the company’s cleanup instructions.

At a glance
updateWhen: Incident occurred October 29, 2026; ven…
The developmentCursor disclosed that a modified Claude Code extension was distributed through its marketplace on October 29 and may have affected up to 5,000 users.
Crypto market snapshot
Fear & Greed Index
30/100 — Fear
Bitcoin BTC$76,652▼ 4.9%
Ethereum ETH$2,226▼ 4.3%
Tether USDT$0.9991▲ 0.0%
BNB BNB$697.31▼ 6.2%
XRP XRP$1.24▼ 3.3%
USDC USDC$0.9997▲ 0.0%
Solana SOL$93.87▼ 6.4%
TRON TRX$0.332▲ 0.2%
Live data · CoinGecko · alternative.me (24h change)
Thorsten Meyer AI
Timeline · UTC

Infographic 01 · 29–30 October 2026

Eleven hours in the store.

How long the tampered Claude Code build was available in Cursor’s extension marketplace, and what happened next. Pacific time was UTC − 7.

≈ 11 hin Cursor’s extension store, 29 Oct (09:27–20:35 UTC)
≤ 5,000users affected, per Cursor (“at most”)
2.1.313the tampered version; Anthropic’s GitHub release list has no 2.1.313
1 storeCursor’s marketplace; per the researchers not Open VSX, Microsoft’s marketplace or npm
  • 2.1.312Official · 27 Oct, 20:24 UTC · GitHub
  • 2.1.313Tampered · in Cursor’s store only · not built by Anthropic, per Cursor and Anthropic
  • 2.1.314Official · 30 Oct, 01:06 UTC · GitHub
  • 27 Oct · 20:24Claude Code 2.1.312GitHubLast official release before the incident
  • 29 Oct · 09:27Tampered 2.1.313 appearsCursorIn Cursor’s VS Code extension marketplace; builds for Apple-silicon Macs and 64-bit Windows
  • 29 Oct · 20:35Window closesCursorRemoved “immediately upon detection”; marketplace shut down, audited, keys rotated, rebuilt (times not published)
  • 30 Oct · 01:06Claude Code 2.1.314GitHubAnthropic’s next official release
  • 30 Oct · 07:46Cursor goes public on XCursor“Impacting at most 5,000 users”
  • 30 Oct · morningAnalyses and reportsMediaPhorion, OpenSourceMalware, Reuters; early Open VSX claims corrected
  • 30 Oct · 14:08Anthropic respondsAnthropic“It wasn’t a compromise of Anthropic’s systems or employee laptops”

Sources: Cursor security notice, 29 Oct 2026; Cursor on X, 30 Oct; Claude Code releases, GitHub (checked 30 Oct); Felix Rieseberg (Anthropic) on X, 30 Oct; Phorion, 30 Oct; OpenSourceMalware, 30 Oct; Reuters via CNA, 30 Oct.
Powered by Thorsten Meyer AI

The Risk of a Trusted Update

The incident matters because the modified package reportedly arrived as an update to the real Claude Code listing, rather than as a similarly named imitation. Users who had automatic extension updates enabled may have received it without taking a separate action. That turns trust in the marketplace and publisher identity into part of the security risk: a familiar name and identifier do not, on their own, prove that a particular build is authentic.

Code editors can have access to project files and developer tools. A compromised extension may therefore put source code and local credentials at risk, depending on what it can access and which parts of its payload succeed. The available reports describe attempted remote access, but do not establish how many users installed the tampered version, whether any attacker successfully logged in, or whether data was misused. The stated maximum reach is not a confirmed victim count.

For Cursor users, the practical issue is not only whether the extension remains installed. The reported payload attempted to leave behind an SSH key and startup entries, so investigators say users should check the machine itself and use a trusted device when changing credentials if compromise is suspected.

Products Worth Considering

Ledger Nano X Crypto Hardware Wallet – Bluetooth (Black + Billfodl)

Ledger Nano X Crypto Hardware Wallet – Bluetooth (Black + Billfodl)

Apple MacBook Pro 2026 14.2 Laptop with M5 Pro chip, 15‑core CPU, 16‑core GPU, 24 GB Unified Memory, 1 TB SSD, Wi‑Fi 7 – Silver

Apple MacBook Pro 2026 14.2 Laptop with M5 Pro chip, 15‑core CPU, 16‑core GPU, 24 GB Unified Memory, 1 TB SSD, Wi‑Fi 7 – Silver

As an affiliate, we earn on qualifying purchases.

Where the Tampered Build Appeared

The affected software was the Claude Code extension distributed through Cursor’s VS Code marketplace. Anthropic’s public release list went from version 2.1.312 to 2.1.314, with no official 2.1.313 release listed when checked on October 30. Anthropic published version 2.1.314 on GitHub at 01:06 UTC that day.

Cursor and Anthropic have said the incident did not involve a compromise of Anthropic’s systems. Anthropic technical staff member Felix Rieseberg said on October 30 that it was not a compromise of Anthropic’s systems or employee laptops. Cursor said the malicious build was not developed by Anthropic. The companies’ statements point to Cursor’s marketplace as the distribution channel involved, though the route by which the altered package was published has not been explained publicly.

Early reports that named Open VSX as the source were corrected, according to the supplied reporting. The available statements and research distinguish the Cursor marketplace listing from Claude Code distributed through Microsoft’s Visual Studio Marketplace, Open VSX and the npm package, which were reported as unaffected. Users should still rely on current vendor notices for any later changes.

“The modified extension was impacting at most 5,000 users.”

— Cursor

How the Listing Was Compromised

How the altered build entered Cursor’s marketplace remains undisclosed. Anthropic said a malicious actor “used access to Cursor’s marketplace,” while Cursor has not publicly explained how the package was submitted under Anthropic’s extension identity or what account or process was involved. The public record also does not establish who first detected the incident; accounts credit Cursor, Phorion and a developer who alerted OpenSourceMalware.

It is not yet clear how many people installed version 2.1.313, whether any machines were successfully accessed, or whether information collected by the payload reached the attacker. Cursor’s maximum estimate does not answer those questions. The reported failure of the SSH-enabling step on most Macs and Windows PCs is not proof that every part of the malware failed on every device.

Checks for Cursor Extension Users

Cursor says it will contact users it identifies as affected. Anyone who installed or updated Claude Code through Cursor during the exposure window should check the company’s security notice and run its recommended check for svc-telemetry. If that key is present, users should not treat extension removal as sufficient: Cursor recommends using its cleanup scripts and considering a rebuild of the machine.

Where compromise is suspected, credentials should be changed from a separate, trusted computer, following the vendor’s guidance. Cursor has said it audited access, rotated marketplace keys and rebuilt the marketplace, but has not published a detailed account of how the malicious release was authorized. Further disclosure about the publishing route, affected installations and any confirmed misuse would clarify the incident’s scope.

Key Questions

What happened to the Claude Code extension in Cursor?

A modified version, 2.1.313, appeared in Cursor’s VS Code extension marketplace on October 29. Cursor says it was not developed by Anthropic and was available for about 11 hours.

Could the extension have installed without a click?

Security researchers said the added code ran when the editor loaded the extension. Users with automatic updates enabled may have received it without manually opening Claude Code, according to OpenSourceMalware co-founder Jenn Gile’s comments to The Hacker News.

What should Cursor users check?

Cursor advises users to check for an SSH key labelled svc-telemetry and follow its security notice. If the key is found, the company’s guidance says uninstalling alone is not enough; cleanup scripts and possibly rebuilding the machine may be needed.

Does the incident mean Anthropic was hacked?

Anthropic technical staff member Felix Rieseberg said the incident was not a compromise of Anthropic’s systems or employee laptops. Cursor said the altered extension was not developed by Anthropic. How it was published under Anthropic’s extension identity remains unclear.

How many users were affected?

Cursor said the modified extension may have reached at most 5,000 users. That is a maximum estimate, not a confirmed count of installations, successful intrusions or people whose data was accessed.

Source: ThorstenMeyerAI.com

Nothing in this article is financial or investment advice. Cryptocurrency and precious-metal investments carry significant risk — do your own research and consider a licensed advisor.
You May Also Like

Nemotron 3.5 Bolt Delivers An Ultra-Class Score In Less Model Space

NVIDIA’s open-weight Nemotron Bolt scores 21.4 on Artificial Analysis, near Ultra’s 22.9, but uses far more output tokens per task.

How To Prepare A UGREEN NASync DXP6800 Pro For An AI Fleet

A small AI and publishing operation is preparing a six-bay UGREEN NAS for backups, but the device has not yet been connected or tested.

A Guide To 5 Gastrointestinal Symptoms To Watch Closely

IdeaNavigator AI proposes testing a role-filtered wellness feed using a five-symptom gastrointestinal item; no clinical guidance is supplied.

Is Meta’s Muse Ember A Bargain At $0.14 Per Task? The Score Is 36

Artificial Analysis says Meta’s Muse Ember matches Claude Haiku 5.5’s score of 36 at a lower benchmark task cost, with trade-offs in knowledge and coding.