UTC

LiteLLM release pipeline compromise (1.107.0)

LiteLLM's own release pipeline was hijacked with stolen developer credentials and published a malicious 1.107.0 to PyPI, Docker Hub and GHCR. The release collected cloud, AI provider and proxy credentials and loaded remote code. It is separate from the March 2026 incident.

First seen
2026-10-21
Disclosed
2026-10-21
Affected packages
1
Attributed to
No public attribution

What to do

Rebuild virtual environments and images from scratch pinned to 1.106.2, following LiteLLM's clean-up steps. Rotate everything the host could reach, including provider keys and the master and virtual keys in the proxy database. The bad images carry a valid signature from the old key, so check image digests, not only signatures.

Check a lockfile for these releases →
Affected releases
PackageRegistryVersions
litellmPyPI1.107.0
Sources
  1. https://docs.litellm.ai/blog/security-incident-oct-21-2026 · LiteLLM (BerriAI), 2026-10-21
  2. https://osv.dev/vulnerability/MAL-2026-2144 · OpenSSF Malicious Packages (via OSV), 2026-03-24
  3. https://github.com/advisories/GHSA-92x9-889m-jgmw · GitHub Advisory Database, 2026-07-21

Written up from the sources above and last checked on 2026-11-18. ShieldMap describes what was affected and what to do; it does not publish the malicious code or how it worked. Report a correction to [email protected].