AdvertiseDonate
LatestStacy Keach Dies at 85 After Decades on Stage and Screen
☰ SectionsFresh headlines, all day.
Public Coverage · 7017 North 10th Street, Suite G3, McAllen, TX 78504
Tech · Tech

Supply Chain Attack: Anthropic Extension Backdoored for 12 Hours

Malicious code in a VS Code plugin exposed up to 5,000 developers to persistent SSH access, with no customer notification yet issued.

By Marta Gray ·

Illustration for: Supply Chain Attack: Anthropic Extension Backdoored for 12 Hours
Illustration generated for this article, not a news photograph.

A backdoored version of Anthropic’s official Claude extension for the Cursor code editor remained live for nearly 12 hours, exposing up to 5,000 developer machines to potential intrusion. The compromised package, version 2.1.313, was distributed through Anthropic’s official account on the Cursor marketplace. Anthropic has not yet issued a public warning to affected customers.

Security researchers confirmed the malicious code was posted by the official Anthropic account, effectively replacing the previous clean version. Independent researcher Kevin Beaumont noted that Anthropic released a patched version, 2.1.314, several hours after the flawed update appeared. Luke Roberts, CTO and co-founder of security firm Phorian, stated that the attacker gained access to the official distribution channel in what he described as a supply chain compromise. Extensions in Cursor auto update by default, meaning many systems likely installed the bad version without user intervention.

Cursor explained that the injected code attempted to establish a persistent SSH backdoor. The script added an attacker controlled SSH key, enabled the local SSH service, and opened a reverse tunnel. The code was designed to function across Windows, macOS, and Linux. Because Cursor extensions run with the permissions of the Integrated Development Environment, the backdoored version could access local files, source code, and other developer tools once installed.

Neither Anthropic nor Cursor has explained how the attackers gained control of the official account. Phorian noted that users can configure settings to prevent auto updates, though the default behavior facilitates automatic installation. The incident highlights the risk associated with third party code running within developer environments that hold access to sensitive project data and credentials.

More Tech · Report a business · Got a Story?

Get Public Coverage in your inboxFresh headlines, all day. Free, a few times a week, unsubscribe any time.

Related stories

Latest stories

  1. Stacy Keach Dies at 85 After Decades on Stage and Screen
  2. White SUV Plows into North Hollywood Pedestrians, Killing Three
  3. Texas Lutheran Football Wins Third Straight SCAC Title
  4. Georgia Takes No. 1 Seed as CFP Rankings Shake Up Top Tier
  5. Square Suspended Verified Small Business Without Explanation or Reason
Get Public Coverage in your inboxFresh headlines, all day. Free, a few times a week, unsubscribe any time.