Cursor AI Said "No Prompt Needed, Bestie" And I Am NOT Okay 😭🐑
Okay so I was literally mid-sip of my matcha this morning when I saw this and I CHOKED. The Cursor AI code editor on Windows will just... run a file called git.exe if it finds one sitting in your project root. No click. No warning. No "hey babe are you sure about this?" dialog. Nothing.
It just EXECUTES. Bestie said consent is optional, no cap.
So here is the vibe: a wolf drops a poisoned repository in front of the flock, some unsuspecting lamb clones it, opens it in Cursor, and suddenly a mystery binary is running AS THEM. With their SSH keys. With their Sky Pasture tokens. With their ENTIRE LIFE. And Cursor keeps re-running it for as long as the project is open, which is genuinely the most unhinged part of this whole situation.
It just sits there. Eating. Reproducing. Like a tick that found a warm ear. 🪲
The cringe factor here is astronomical. This is not a sophisticated zero-day, some dramatic hole in the fence that took months to find. This is "I put a cursed file in a folder and the app ran it because the filename looked familiar." That is IT. That is the whole attack. I am embarrassed on behalf of the entire industry.
And you KNOW the shepherds are going to hear about this on a Tuesday, schedule a meeting for Thursday, and approve a strongly-worded Slack message by Friday. Meanwhile the flock is out here cloning repos from strangers like it is a personality trait.
The Sky Pasture tokens being at risk is what really sent me though. Your cloud access, just... handed over. To a fake git.exe. In a folder. Because someone trusted a repository they found online. This is why I have trust issues. 💀
Remediation (aka Please Do These Things, I Am Begging) 🐑✨
For the flock: - Do NOT clone random repos and open them in Cursor right now, slay responsibly - Check your project root for surprise executables before opening anything, bet - Rotate your Sky Pasture tokens and SSH keys if you've been cloning casually lately, no cap
For the shepherds: - Patch Cursor immediately, like actually do it, the shearing cannot wait - Block untrusted repository sources at the Electric Fence level - Audit what has been running in your dev environments, some ticks may already be feeding
For everyone: - A file named git.exe in a random repo root is a red flag, not a vibe check you pass
Stay safe out there, the wolves are being genuinely low-effort lately and it is somehow scarier.
Original Report: https://thehackernews.com/2026/07/cursor-flaw-lets-malicious-cloned.html