See all news
LiteLLM
Cybersecurity

A poisoned dependency! LiteLLM confirms malware in its version 1.107.0

LiteLLM confirmed that its release process was compromised and distributed malicious artifacts of version 1.107.0 on PyPI and container registries. The threat included credential theft and remote code execution capabilities. The project removed the compromised packages and published guidance for those who installed the files during the identified windows.

The incident illustrates the risks of the software supply chain. Modern applications depend on automatically published libraries; if an attacker tampers with the distribution process, a seemingly normal update can carry malicious code to many organizations.

According to LiteLLM's official advisory, on October 21 compromised files of version 1.107.0 were published on both PyPI and Docker registries. The project reported that the attackers used the credentials of three developers to manipulate the release pipeline. The affected packages were removed and the access involved was revoked. The maintainers stated that previous versions were not compromised and that their private enterprise registry was not affected.

Teams that installed the identified artifact should treat their secrets as potentially exposed, following the project's instructions. The response should not be limited to rolling back a dependency: it also requires reviewing credentials and available logs.

At a glance

WhatLiteLLM version 1.107.0 and some container images were compromised with malware capable of stealing secrets and enabling remote access.
WhenThe incident occurred on October 21, 2026, with specific exposure windows on PyPI and container registries.
WhereThe distribution affected PyPI, Docker Hub and GHCR, with potential impact on systems that installed or ran the compromised artifacts.
HowLos atacantes utilizaron accesos comprometidos de desarrolladores para alterar la publicación y distribuir artefactos que contenían código malicioso.
WhyA single compromised dependency can expose the credentials of many users; securing software publishing is crucial to prevent cascading attacks.

Build your digital presence

Start today: write to us and we’ll reply within 24 hours.