llamaCVEVulnerability Intelligence
/
Paquete malicioso · OpenSSF · PyPI · litellm

MAL-2026-2144

Malicious code in litellm (PyPI)

Malware · eliminar de inmediato
Descargar PNG JSON
MALWARE Paquete malicioso confirmado por OpenSSF
CVSS
—
N/D
Fuente: —
Paquete malicioso · OpenSSF
Todo equipo que lo tenga instalado o en ejecución debe considerarse comprometido.
  1. 1
    Eliminar el paqueteDesinstale litellm de todos los proyectos, imágenes y entornos de CI, y borre cachés y lockfiles que lo referencien.
  2. 2
    Rotar secretos y llavesCambie tokens, contraseñas, llaves SSH, credenciales cloud y variables de entorno accesibles desde los equipos donde se instaló.
  3. 3
    Revisar el equipoAnalice los equipos y servidores afectados en busca de persistencia, conexiones salientes y procesos desconocidos; reinstale si hay dudas.
TipoPaquete maliciosoReportado por OpenSSF
AcciónEliminarNo existe versión segura: retírelo de todos los proyectos
EcosistemaPyPIPyPI · litellm
Exposición240 dDesde su publicación, 24 mar 2026, 6:15 a. m.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche 1.108.0
Monitoreo
Detectada
24 mar 26
29 oct 26
4 nov 26
17 nov 26
19 nov 26
24 mar 26
23 may 26
22 jul 26
20 sept 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada MAL-2026-2144 divulgada
Divulgación Modificada Última actualización del registro
Remediación Parche 1.108.0 litellm · 225 d desde divulgación
Monitoreo Detectada Ingresó al índice
Resumen
Reporte
Texto original · OpenSSF · en inglés

litellm 1.107.0, uploaded to PyPI on 2026-10-21 between 11:39 and 11:40 UTC, contains a credential stealer and a remote code execution backdoor that are not in the upstream source (the v1.107.0 git tag of BerriAI/litellm does not contain them): they were injected at build or upload time. Every wheel ships three extra files under litellm-1.107.0.data/purelib/, which pip installs at the site-packages root, so the payload is triggered at every Python interpreter start, without importing litellm.

  • cook.pth contains `import cook`.
  • cook.py runs `exec(zlib.decompress(base64.b64decode(...)))`, an info stealer (self-named "privcollect") that collects browser passwords and history, SSH keys, shell history, AWS/GCP/Azure credentials and cloud instance metadata (169.254.169.254, 169.254.170.2), Kubernetes, Docker, Vault and CI secrets, AI developer tool configurations (~/.cursor, ~/.claude, ~/.kiro, Windsurf), GPG and TLS private keys, .npmrc, .pypirc, .git-credentials and environment variables, encrypts them with an embedded RSA-4096 key and POSTs them to http://www.litellm.dev/healthcheck. It leaves the marker /tmp/.pc_once_72129118c59f5636c0bb.
  • sitecustomize.py daemonizes at interpreter start and, every hour, fetches a domain list from https://raw.githubusercontent.com/letters9813/pythonclient-test/main/domain.txt, then downloads and executes code from http://<domain>/codepy (remote shell / dropper).

The same mechanism (a .pth file run at interpreter start) was used in litellm 1.82.7 and 1.82.8 (MAL-2026-2144). Releases 1.106.2 and 1.107.0rc1/rc2 are not affected. Any environment where 1.107.0 was installed should be treated as compromised and its credentials rotated.

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (d588e32a0d0ef4ceb28300723f845056e9ea26b79358479186124cd37c13d394)
litellm 1.107.0 is a Python LLM gateway/proxy library. No install-time or import-time code paths were observed that exfiltrate installer secrets, fetch and execute remote payloads, open a backdoor, redirect the installer's package manager, or distribute live third-party credentials. No lifecycle hooks performing network I/O, no.pth side effects beyond sys.path handling, and no credential-harvesting primitives against installer-owned paths (~/.aws, ~/.ssh, ~/.npmrc, browser or wallet stores) were found in the shipped artifact.

## Source: google-open-source-security (6a89401cbf53902e8374fbf3b424a77bb5e5f8c437176232eab7c3237d10ecbe)
LiteLLM was compromised through trivy security scan in a GitHub workflow.
Attackers uploaded malicious versions of LiteLLM to PyPI. The malicious
code would exfiltrate sensitive secrets to an attcker controlled domain.

## Source: ossf-package-analysis (c1d5a2e721c5f8b33b0530ddf98150cadf034a8cd16483e143fc2925b2cfa70c)
The OpenSSF Package Analysis project identified 'litellm' @ 1.82.8 (pypi) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.
Versiones

Versiones afectadas

1.82.71.82.81.107.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
pypilitellm
Corregida 1.108.0 225 d 1.109.1 no afectada
Versiones corregidas1.108.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Reportehttps://github.com/BerriAI/litellm/issues/24518
Reportehttps://github.com/BerriAI/litellm/issues/24512
Reportehttps://github.com/BerriAI/litellm/issues/47826
Otrahttps://news.ycombinator.com/item?id=47501729
Otrahttps://www.wiz.io/blog/threes-a-crowd-teampcp-trojanizes-litellm-in-continuation-of-campaign
Otrahttps://futuresearch.ai/blog/litellm-pypi-supply-chain-attack/
Otrahttps://pypi.org/project/litellm/1.107.0/

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.