Return to Threats

LiteLLM Suspects GitHub Token Leak in AI Gateway Logs Behind Malicious Package Release

thehackernews.com 2026-10-22 AI supply chain Critical
Run AI Security Assessment Talk to AI CISO

Executive Summary

Threat actors compromised LiteLLM’s release pipeline and published a malicious package containing a credential stealer and backdoor. Organizations using LiteLLM, Docker Hub, or PyPI should assess exposure and secure related credentials and deployment pipelines.

What Happened

LiteLLM on Wednesday disclosed that threat actors compromised "multiple independent security controls" to push a malicious version of the Python package containing a credential stealer and a backdoor. On October 21, 2026, LiteLLM's release pipeline was compromised to push 1.107.0 to the Docker Hub registry and the Python Package Index (PyPI) repository. The incident took place around 4:00 a.m.

Affected Products

  • LiteLLM
  • LiteLLM version 1.107.0
  • Docker Hub
  • Python Package Index (PyPI)

Vulnerability / Attack Technique

Malicious package release through compromised software supply chain

Technical Mechanism

Threat actors compromised multiple independent security controls in LiteLLM’s release pipeline and pushed version 1.107.0 to Docker Hub and PyPI. The released Python package contained a credential stealer and a backdoor; LiteLLM suspects a GitHub token leak in AI gateway logs.

AI Security Category

LLM03:2025 Supply Chain

Part of the AI Supply Chain and AI SBOM topic.

Relevant Frameworks

LLM03:2025 Supply ChainMITRE ATLAS: Credential AccessMITRE ATLAS: PersistenceMITRE ATLAS: Initial Access

RealGround Analysis

AI gateway dependencies can become a high-impact entry point into applications, credentials, and deployment environments. Teams running AI agents or LLM applications should maintain an inventory of AI-related packages and containers, enforce trusted build and release controls, and monitor gateway logs for exposed tokens.

Recommended Controls

  • Inventory LiteLLM versions, containers, and transitive dependencies using an AI-focused SBOM.
  • Immediately review use of LiteLLM version 1.107.0 and replace it with a verified non-malicious version.
  • Rotate GitHub tokens and other credentials that may have appeared in AI gateway logs.
  • Require signed artifacts, protected release branches, multi-party approval, and isolated build environments for AI package releases.
  • Scan AI gateway logs for secrets and implement automated redaction before storage or transmission.

Related RealGround Service

AI Agent SBOM and LLM Mapping · or start with the free AI Agent Security Scanner.

Sources

thehackernews.com: https://thehackernews.com/2026/10/litellm-suspects-github-token-leak-in.html

Summary and analysis written by RealGround from the source above; last updated 2026-10-22.

Talk to AI CISO