Why Auto-Updating Editor Extensions Put Developer Laptops at RiskWhy Auto-Updating Editor Extensions Put Developer Laptops at Risk
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Auto-updating editor extensions is the riskiest setting on a dev laptop.
The backdoored Claude Code extension on Cursor's marketplace, versions 2.1.312 and 2.1.313, ran the moment the editor loaded it. No click, no prompt. It added an SSH key to authorized_keys, opened a tunnel out, and reported the names of any environment variables that looked like keys or tokens. Anthropic's staff say those versions never went out through its own channels.
Most of the Hacker News thread asks for signed extensions. Signing would help, but it proves who signed the file, not that the right person did. It also does nothing once a bad version lands on every machine overnight.
The Claude Code plugins I run come from a repo I own, and an install only changes when I run the update myself. That's slower, and it means a bad push can't reach my laptop until I choose to take it.
Some in the thread wait a week before taking any extension update. How long do you wait?
Joe's avatar
Source: https://phorion.io/blog/offical-claude-code-vsx-compromise
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started