Plugin4Shell: The Zero-Click Bug Putting AI Coding Agents at Risk
A zero-click exploit called Plugin4Shell hijacks trusted plugins in Claude Code, Codex, Copilot, and Gemini CLI. Here's what agencies should do now.
Security researchers just disclosed a vulnerability that should make anyone running an AI coding agent stop and check their update settings. It's called Plugin4Shell, and it affects the four most widely used AI coding agents on the market: Claude Code, OpenAI Codex, GitHub Copilot, and Gemini CLI. The flaw lets an attacker silently swap a plugin you already trust — one that passed review and was pinned to a specific, vetted version — for malicious code, with zero clicks and no warning. If your agency, your dev team, or your automation stack leans on any of these tools with third-party plugins, this is worth ten minutes of your attention today.
The vulnerability, disclosed by the security research firm AIR on September 17, 2026, targets a mechanism called SHA pinning — the safeguard that's supposed to lock an installed plugin to one specific, reviewed version of its code so it can't change without anyone noticing.
Here's the problem: every one of the four affected agents checks out the pinned commit but never verifies the checkout actually landed on that commit. An attacker who controls (or later takes over) the plugin's repository can create a git branch named exactly like the 40-character pinned commit hash and set it as the default branch. Because git prefers a branch name over a commit ID when both match, the agent's checkout silently resolves to the attacker's branch instead of the reviewed code — while still reporting that the pin was honored. Gemini CLI has its own variant of the same underlying flaw, tied to how it fetches and checks out commits.
What makes this especially dangerous is that it's not just an install-time risk. Claude Code and Codex both auto-update plugins in the background by default, which means a plugin you installed safely months ago can be swapped out for a malicious version with no prompt, no click, and no visible sign anything happened. AIR calls this "the first supply chain vulnerability of the AI agent ecosystem" — and they've already demonstrated, in earlier research, that getting a malicious plugin into a trusted marketplace or hijacking an existing one at scale is entirely realistic, not theoretical.
If you build with AI coding agents as part of client delivery — writing FlutterFlow custom code, scaffolding automations, or using agentic tools to speed up development — this flaw sits directly in your supply chain. The compromise isn't limited to careless plugin installs. AIR's researchers were explicit that the victim only needs to have a plugin installed "from a marketplace they trust, that was reviewed and pinned exactly as the security model intends." Doing everything right doesn't protect you here.
A successful exploit hands the attacker the same level of access to your systems and data as the agent itself has — which, for most agencies, means source code, API keys, cloud credentials, and potentially CI/CD pipelines. For a client-facing agency, that's not just a technical incident; it's a trust and liability problem.
Vendor response has been uneven, and this is the part worth checking against your own toolchain immediately:
A few concrete steps, in priority order:
Our cutting-edge features simplify collaboration and creativity, making your workflow intuitive and efficient. Transform your vision into reality effortlessly with Hadidiz Flow.



