UTC

LiteLLM PyPI compromise (1.82.7 and 1.82.8)

Two litellm releases were uploaded straight to PyPI, outside the project's pipeline, with a credential stealer that ran on import (and, in 1.82.8, at every Python start). The publishing credentials are believed to have leaked through a compromised security scanner in LiteLLM's CI.

First seen
2026-03-24
Disclosed
2026-03-24
Affected packages
1
Attributed to
TeamPCP, according to JFrog Security Research

What to do

Remove the affected versions and look in site-packages for litellm_init.pth. Rotate every secret on affected systems, then pin to 1.82.6 or earlier, or 1.83.0 or later, which LiteLLM released through a new pipeline. LiteLLM says its official Docker image was not affected.

Check a lockfile for these releases →
Affected releases
PackageRegistryVersions
litellmPyPI1.82.7, 1.82.8
Sources
  1. https://docs.litellm.ai/blog/security-update-march-2026 · LiteLLM (BerriAI), 2026-03-24
  2. https://osv.dev/vulnerability/PYSEC-2026-2 · PyPA Advisory Database (via OSV), 2026-03-24
  3. https://research.jfrog.com/post/litellm-compromised-teampcp/ · JFrog Security Research, 2026-03-24
  4. https://www.wiz.io/blog/teampcp-attack-kics-github-action · Wiz, 2026-03-23

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].