If you use Cursor to write code with AI, there's a security story you need to hear. A tampered version of the Claude Code extension sat in Cursor's marketplace for about 11 hours, and up to 5,000 people may have downloaded it. It wasn't just a buggy add-on. According to Cursor and independent security researchers, it stole personal data and opened a remote door into users' computers.
What happened
A fake version in a trusted store
Here's the short version. Cursor is an AI-powered code editor. An extension is an add-on, like an app you install on your phone. Cursor's marketplace is the built-in app store for those add-ons. For roughly 11 hours, a substituted version of Claude Code 2.1.313 was available there. The official product is Claude Code, and version 2.1.313 is the specific release named in the notice. The copy in the store was not the clean original.
Security researchers call this a trojanized extension. That means malware dressed up as legitimate software. The extension also acted as a backdoor, which is a hidden entrance that lets an attacker slip past normal login screens. In practical terms, the malicious code could hand hackers remote access to a PC. Remote access is like giving someone a copy of your house key and letting them walk in while you're at your desk.
What a backdoor actually does
Cursor moved fast once the problem was found. It removed the extension and got the attacker's server shut down. The company also published an official security notice with cleanup instructions. The key number is 5,000. That's the upper estimate of downloads for the infected version, not a confirmed count of people whose data was actually stolen. Independent write-ups from Help Net Security, Phorion, and StepSecurity describe a trojanized extension with an SSH backdoor. SSH is a common way to log in to another computer remotely. That combination is serious because it can turn a normal work session into an open door for an attacker.
If you think you're affected, start with Cursor's own notice: Claude Code extension security notice. It's the source of truth for cleanup, and it's free.
What it means for you
Most people don't need to understand the malware's code. They need to understand what a stranger with remote access could do with a laptop that's logged into email, cloud storage, and work systems. The risk isn't abstract. It lands in ordinary places.
At home
You may use Cursor on a personal laptop that also holds family photos, tax files, and saved passwords in the browser. A backdoor doesn't need to steal every file to cause trouble. It can watch, copy, or open a path for more malware. If the browser is already logged in, an attacker may not need your password at all. That's why changing passwords from a different, clean device matters if you were affected. The 5,000 figure is a download estimate, so not everyone in it was necessarily compromised, but the safe assumption is to treat an infected install as exposed until you've cleaned it.
At work
At work, the stakes jump. A code editor often has access to source code, cloud dashboards, internal chat, and sometimes production systems. Remote access to that machine can expose client data, API keys, and company credentials. API keys are like passwords for software. If they're sitting in a config file, malware can scoop them up. Tell your security or IT team if you installed Claude Code 2.1.313 on a work machine. Don't wait until you're sure something bad happened. Fast reporting is cheaper than a cleanup later.
For a small business
For a small business, one compromised laptop can reach invoices, customer lists, payment portals, and shared drives. The attacker may not go after the business directly. They can use the machine as a stepping stone. That's why Cursor's server takedown matters, but it doesn't automatically clean an already infected computer. If you run a team, ask who installed the extension and on which devices. Then rotate the passwords and keys those devices could reach.
For students
Students often use the same laptop for coursework, email, and social accounts. A compromised machine can mean lost assignments, stolen login details, or a hit to your reputation if someone posts from your account. The fix isn't to swear off AI tools. It's to install add-ons from official sources, check the publisher, and keep the list short. If you downloaded the bad version, follow Cursor's notice and change your school and email passwords.
For creators
Creators live in a mix of cloud folders, design files, and social accounts. A backdoor on the laptop can expose unfinished work, client contracts, and brand accounts. It can also give someone enough access to lock you out or impersonate you. If you use Cursor to build a portfolio site or automate content, treat the machine as part of your business. Clean it, then turn on two-factor authentication. Two-factor authentication is the second lock: a code on your phone in addition to your password.
For side income
If you freelance or run a side hustle, your laptop may hold invoices, payment details, and client logins. Remote access can turn a small project into a financial mess. The attacker doesn't need to empty a bank account in one go. They can wait, collect information, and strike later. The practical move is boring but effective: remove the bad extension, follow the official cleanup steps, change passwords from a clean device, and check your accounts for unusual logins. If you want to test AI prompts without installing another extension, use a free browser-based tool from mykreatool.
How to try it right now
Try this safety check now, even if you think you're fine. The free option comes first: read Cursor's official notice. It costs nothing and it's the source of truth for cleanup. Open Claude Code extension security notice.
Free check first
1. Open Cursor. Go to the Extensions panel. This is the add-ons list inside the editor.
2. Look for Claude Code. Check the version number. If you see 2.1.313, remove it.
3. Don't stop at removal. Follow Cursor's notice step by step. It was written for this exact incident.
4. If you're on a work laptop, message your IT or security contact. Include the extension name and version. Don't send passwords over chat.
5. Open your browser's password manager or the security settings for your main accounts. Change passwords from a different device you trust. Start with email, GitHub, cloud storage, and banking.
Lock down your accounts
After cleanup, turn on two-factor authentication everywhere it's offered. Check active sessions and sign out devices you don't recognize. Revoke API keys and tokens that were stored on the affected machine. A token is a digital key that lets an app act on your behalf. If you're not sure whether a key was exposed, rotate it. That means replace it with a new one and disable the old one. Finally, run a full antivirus scan with the security tool you already trust. No scanner is perfect, but it's a sensible second pass after removing a known bad extension.
Upsides and what changes
The obvious downside is that a trusted marketplace briefly hosted malware. The upside is the response. Cursor pulled the extension and got the attacker's server disabled. Researchers published independent analyses quickly. Users got a clear notice instead of silence. That's how a mature software ecosystem should behave when something goes wrong. Expect more scrutiny around AI coding extensions. Marketplaces will likely tighten review, publishers will face more verification, and users will pay closer attention to version numbers and permissions. That's a healthy change. An extension is not a harmless sticker. It runs inside your editor and can often reach files, network connections, and credentials. The Claude Code 2.1.313 incident makes that concrete. It also gives teams a reason to review which add-ons they actually need.
Limitations
There are real limits to what we know. The 5,000 figure is an estimate of downloads, not a confirmed list of victims. Some people may have downloaded the extension without ever opening it. Others may have opened it and still not been targeted. Cursor's notice is the best official source, but incident details can change as the investigation continues. Removing the extension doesn't prove a machine is clean, and changing passwords doesn't undo data that was already copied. No article can tell you whether your specific laptop was accessed. If you need certainty for a business or client device, get help from a qualified security professional and keep records of what you did.
Conclusion
One action for today: open Cursor, check whether Claude Code 2.1.313 is installed, and remove it if it is. Then follow Cursor's official notice. The bigger lesson is simple. AI tools are powerful, but every extension is code running on your machine. Treat add-ons like keys to your digital life. Check the publisher, watch the version, and keep the list small. If you were one of the up-to-5,000 downloaders, don't panic. Act in order: remove, read the notice, change passwords from a clean device, turn on two-factor authentication, and tell your team if work data was in reach. That's a boring checklist, and that's exactly why it works.
Comments 0