Back to blog
LiteLLMsupply chainPyPIAI agentsAPI keys

LiteLLM 1.107.0 backdoored on PyPI and Docker: a cloud and AI key stealer inside your agents' gateway

Published on 2026-10-22 · Updated on 2026-10-246 min readCleanIssue

> TL;DR: On October 21, 2026, LiteLLM's release pipeline was compromised and pushed a malicious 1.107.0 to PyPI and Docker Hub. It carried a credential stealer: cloud, Kubernetes, SSH keys, browser cookies, and authentication files for Codex, Claude, Gemini and Cursor. This is the second such attack on LiteLLM this year. All earlier versions are safe, the latest being 1.106.2. If you installed 1.107.0, treat your credentials as compromised.

What happened

  • Access: according to LiteLLM, the attacker used the GitHub accounts of three engineers, apparently through stolen GitHub CLI OAuth tokens. One account changed the pipeline and triggered the release, a second approved it, a third deleted the workflow records.
  • Window: the package stayed on PyPI from 11:39 to 13:23 UTC. Docker images v1.107.0, latest, main-latest and main-stable served the bad build from 11:46 to 14:20 UTC.
  • Persistence: the malicious code sat in Python startup files. It runs whenever Python starts in the affected environment, even if the application never imports LiteLLM.
  • Use: Wiz saw the stolen credentials in use about four and a half hours after exfiltration. The attacker tested AWS keys taken from CI runners and Kubernetes nodes to reach models on Amazon Bedrock.
  • The malware also tried to read the database of LiteLLM proxy deployments, which holds model provider keys. Researchers note this shows intent without proving success.

    Why this is an AI agent incident

    LiteLLM is the gateway many teams place between their agents and model providers. It holds the keys to every model, the budgets and often prompt logs. Compromising the gateway means gaining the power to spend on the company's behalf, and sometimes to read what agents send.

    What to do now

  • Search for 1.107.0 in your environments: developer machines, CI runners, Docker images pulled with latest on October 21.
  • If you find it, rotate every credential reachable from the machine: cloud keys, GitHub tokens, SSH keys, model provider keys, and coding assistant authentication files.
  • Pin versions and hashes of your dependencies. Do not use latest in production.
  • Watch model provider billing: abnormal usage on Bedrock or elsewhere is the first sign of a stolen key.
  • The takeaway

    The most exposed link in an agent architecture is not always the model. Here, an OAuth token on a developer's machine opened the door to the gateway serving every agent.

    Building software? CleanIssue performs security audits for your product in real-world conditions, no source code access needed. For a first read of your exposure, start with an external review of your application.

    Want to know what your AI agent can do?

    Tell us about your agent, its tools, and client context. We will come back with the right review scope.

    Discuss your audit