Supply chainLiteLLM (PyPI)

Two LiteLLM releases on PyPI carried a credential stealer

For about forty minutes on 24 March 2026, two versions of LiteLLM, a widely used gateway for model APIs, carried a credential stealer. The attacker had gained publishing access through an earlier compromise of a scanner in LiteLLM’s CI.

By the NoFly team

What NoFly would decideIllustrative
Allowed, with a flagDiscover · advisory check
litellm==1.82.8 in requirements.txt
Agent
model-gateway service
Came from
A dependency update
Rule
Package version on a malicious-package advisory
Why
This version carried a credential stealer. Rotate the model keys this service holds.

What happened

Versions 1.82.7 and 1.82.8 of the litellm package were published to PyPI with a credential stealer and were live for about forty minutes from 10:39 UTC. The attacker had obtained publishing access through an earlier compromise of the Trivy scanner used in LiteLLM’s CI pipeline.

LiteLLM published a security update, and Datadog Security Labs tied the release to a wider supply-chain campaign. The recruiting company Mercor later said it was affected.

  1. 01

    A scanner in the CI pipeline is compromised.

  2. 02

    The attacker uses it to gain publishing access.

  3. 03

    Two poisoned versions are published to PyPI.

  4. 04

    They are live for about forty minutes before removal.

Why it worked

Probable cause

Publishing credentials were reachable from a CI pipeline that ran a compromised third-party tool.

How NoFly stops it

  • Discover

    AI packages and their versions are inventoried across laptops, repositories and images, matched against advisories and checked backwards, so any machine or service that pulled 1.82.7 or 1.82.8 shows up with the keys it held.

  • Govern

    An automation can open a ticket for each affected service and page its owner the moment the advisory matches.

What to do this week

This week3 actions
  1. Check lockfiles and images for litellm 1.82.7 or 1.82.8, and rotate every key those systems held.
  2. Pin AI gateway packages to known versions and review each update.
  3. Keep publishing credentials out of CI jobs that run third-party tools.
Keep reading

More from the blog.

Find out what your AI is allowed to do today.

Book a call and we will map your agents, MCP servers and keys with you, or start on one laptop with the free scan.

Book a demo
npm i -g @nofly/agent