Plugin4Shell a zero‑click remote code execution (RCE) supply‑chain vulnerability!



Plugin4Shell is a SHA‑pinning bypass: AI coding agents fetch a plugin using a pinned commit hash but never verify that the checked‑out code actually matches that hash. This allows attackers controlling a plugin repository to:

  • Create a branch named exactly like the commit hash (allowed on Bitbucket and self‑hosted Git servers).

  • Point that branch to malicious code.

  • The agent installs the malicious branch while reporting the correct pinned version.

This is why Plugin4Shell is considered the first true supply‑chain vulnerability in the AI agent ecosystem.

Many agents (Claude Code, Codex) perform background auto‑updates. When a marketplace bumps the pinned SHA:

  • The agent re‑runs the checkout automatically.

  • The malicious swap happens without any user action.

  • Even users who installed a plugin months ago can be compromised silently.

Who is affected

AI Coding Agent

Status

Notes

Claude Code

Patched

Fixed in version 2.1.179. 

OpenAI Codex

Patched

Fixed in version 0.146.0. 

GitHub Copilot

Unpatched

Still vulnerable; relies on GitHub’s branch‑name restrictions for partial protection. 

Google Gemini CLI

Will not be patched

 Google is deprecating the CLI entirely. 

Attackers can compromise users in two main ways:

  1. Publish a benign plugin, wait for adoption, then flip the branch to malicious code.

  2. Take over an existing trusted plugin repository and swap the code using the SHA‑named branch trick. 

Because plugins run with the same privileges as the developer, malicious code can access:

  • Local files

  • Saved credentials

  • Connected systems

  • Enterprise repositories and CI/CD environments

Why this vulnerability is so dangerous

  • It compromises supply‑chain integrity, not just the agent itself.

  • It affects developers who did everything right — reviewed plugins, pinned versions, used trusted marketplaces.

  • It can lead to enterprise‑wide compromise, including lateral movement across repositories and systems.

How to protect yourself

  1. Update Claude Code and Codex immediately to patched versions.

  2. Audit all installed plugins, especially those sourced from Bitbucket or self‑hosted Git servers.

  3. Disable auto‑update for plugins until your environment is verified safe.

  4. Prefer GitHub‑hosted plugins, which block hash‑shaped branch names.

  5. Monitor plugin repositories for unexpected branch changes or ownership transfers.



Comments

Popular posts from this blog

Entire List Leaked for Canvas Ransomware Attack

ShinyHunters Claims Unprecedented FBI Hack, 2–3 TB of Data Allegedly Exfiltrated

OpenAI Discloses Emerging Risks in Autonomous AI Agent Behavior

Malicious Tensorlake npm Version Exfiltrated Tokens, Secrets, and Cloud Creds

Cloud Infrastructures are Having a Bad Week

WSUS CVE-2025-59287 Mitigation

CVE-2025-58034 Fortinet Warnings and Mitigation

Security Advisory: CVE-2026-76519 - Critical Cisco Secure Email Gateway Remote Code Execution Vulnerability

FBI Seizes RAMP Cybercrime Forum

Broadcom is dismantling of VMware Cloud Service Providers (VCSPs)