Back to Feed
Supply ChainNov 13, 2026

Your pinned MCP server may not be as pinned as you think

MCP servers can drift from pinned versions, exposing AI coding assistants to dependency risks.

An MCP server configured for a fixed release was found to run with 15 different dependency sets over five weeks due to its launcher resolving fresh packages from PyPI, bypassing the lock file. This "pinning drift" affects 23 of 69 packages, including critical libraries, and exposes AI coding assistants that often hold user credentials. A similar Shai-Hulud worm variant on PyPI previously targeted AI coding assistant keys.

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run Corelight?

Get an email when a new story names Corelight, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

The lesson from this incident

Full lesson

An MCP server believed to be pinned to a fixed release was silently running with 15 different dependency sets over five weeks because the launcher resolved fresh packages from PyPI rather than honoring the lock file, a phenomenon dubbed 'pinning drift.' This affected 23 of 69 packages, including critical libraries that AI coding assistants rely on while often holding user credentials. The risk is compounded by precedent: a Shai-Hulud worm variant on PyPI previously targeted AI coding assistant keys, confirming that attackers actively exploit this attack surface. This matters because developers assume pinned environments are deterministic and safe, yet the actual runtime environment can silently diverge, introducing malicious or vulnerable code without any visible warning.

What helps against this

How we list vendors

Indicators of Compromise

Extracted by AI from the linked source. Not reviewed by an editor. How this works

  • malware — Shai-Hulud

Entities

MCP (product)AI coding assistants (technology)Corelight (vendor)Python Package Index (technology)