The Claude Code Extension Hack That Should Worry Every Developer

Robert Moore · 2026-10-30

So here's something that should make you pause before you hit "install" on your next extension. Researchers just found that the official Anthropic Claude Code extension got compromised on the Open VSX registry, and it was quietly planting a persistent SSH backdoor on infected machines. Yeah. That's the kind of thing that keeps people up at night. The trail eventually led back to the Cursor Marketplace, which is why the AI coding platform briefly pulled the whole service down to scrub the malware out. Cursor confirmed the move with a short statement: "We identified a security incident." Not exactly comforting, but at least they acted fast. ### What actually happened here If you're not deep in the dev tooling world, Open VSX is the open-source extension registry that powers a lot of VS Code-compatible editors. It's not the official Microsoft marketplace, but plenty of tools pull from it. And that's exactly what made this compromise so sneaky. The malicious version of the Claude Code extension wasn't sitting on some sketchy third-party site. It was on a registry developers trust. Once installed, it set up an SSH backdoor that stuck around, meaning even after you thought you'd cleaned things up, an attacker could still slip back in. - The extension was live on Open VSX before anyone caught it - The backdoor was persistent, not a one-time payload - The root cause traced back to the Cursor Marketplace compromise - Cursor took the service offline temporarily to remove the malware ### Why this matters more than you think We've gotten really comfortable installing extensions the way we grab coffee, quickly, without a second thought. But every extension is code running with your permissions. It can read your files, touch your credentials, and now apparently open a door for someone else to walk through later. For anyone using antidetect browsers or managing multiple online identities, this is a wake-up call. A backdoor on your dev machine doesn't just expose your code. It can expose every session, every profile, and every account you're juggling. If you're running the best antidetect browser setup to keep profiles isolated, a compromised extension on the host machine can undo a lot of that careful work. ### What you should do right now A few practical steps, no panic required: - Audit your installed extensions and remove anything you don't actively use - Check whether you're pulling from Open VSX or the official marketplace, and know the difference - Rotate SSH keys and credentials on any machine where the extension ran - Watch for unusual outbound connections, especially anything hitting odd IPs on port 22 - Keep an antidetect browser layer between your sensitive accounts and your dev environment ### The bigger lesson Supply chain attacks aren't new, but they're getting more targeted. Attackers aren't just going after random npm packages anymore. They're going after the tools developers trust most, the ones we install without blinking. The Claude Code compromise is a reminder that "official" doesn't automatically mean "safe." So next time you install an extension, take thirty seconds. Read the publisher. Check the reviews. Ask yourself if you actually need it. That tiny pause might be the difference between a clean machine and a persistent backdoor you never see coming.