Cursor Bug Runs Malicious Code in Cloned Repos on Windows

Robert Moore · 2026-07-15

Imagine opening a project in your code editor and, without any warning, a hidden program runs on your machine. That is exactly what happens with a newly discovered flaw in Cursor, the popular AI-powered code editor. On Windows, if a repository contains a file named git.exe in its root folder, Cursor executes it automatically. No click, no approval dialog, no prompt. The binary runs with your full user permissions, accessing your source code, SSH keys, and cloud tokens. And it keeps running as long as the project stays open. ### How the Flaw Works The issue is deceptively simple. Cursor, like many editors, relies on Git for version control. When you open a repository, it looks for Git executables in the project path. If a malicious file named git.exe is placed there, Cursor runs it without any verification. This is not a theoretical exploit. It is a practical attack vector that can be triggered by cloning a repository from an untrusted source. ### Why This Is Dangerous For developers, this is a nightmare scenario. Your SSH keys give access to servers, your cloud tokens unlock services like AWS or GitHub, and your source code is your intellectual property. A single malicious binary can steal all of that. And because Cursor re-runs the file every time the project is active, the attack persists. Even if you close and reopen the editor, the binary executes again. ### Who Is at Risk Any developer using Cursor on Windows is vulnerable. The flaw does not affect macOS or Linux users, but Windows remains the most common desktop OS for many developers. If you work with cloned repositories from public sources, especially those you do not fully trust, you are at risk. This includes open-source contributors, freelancers, and enterprise teams. ### What You Can Do Right Now There is no official patch yet, but you can protect yourself. Here are some practical steps: - Always inspect repositories before opening them. Look for unexpected executables in the root folder. - Use a dedicated tool like an antidetect browser to manage your digital identity. This adds a layer of separation between your work and potential threats. - Run Cursor in a sandboxed environment or a virtual machine for untrusted projects. - Disable automatic Git execution in Cursor settings if possible. ### Why Antidetect Browsers Matter Here This flaw highlights a broader issue: your digital identity is only as secure as the tools you use. Antidetect browsers, like the ones we review on this site, help you manage multiple profiles and isolate activities. They prevent cross-contamination between your personal and professional work. For developers handling sensitive code, using an antidetect browser for web-based tasks can reduce the attack surface. ### The Bigger Picture Software flaws like this one remind us that trust is a fragile thing. We assume our tools are safe, but every line of code is a potential vulnerability. The best defense is a layered approach: use secure tools, verify your sources, and never assume a program is safe just because it came from a popular repository. ### Final Thoughts Cursor is a powerful editor, but this flaw is a serious wake-up call. Until a fix is released, treat every cloned repository with suspicion. And consider using an antidetect browser to manage your online identities. Your data is worth protecting. *This article is for informational purposes only. Always verify security updates from official sources.*