LiteLLM's release pipeline was compromised via stolen GitHub CLI OAuth tokens on three developer accounts. Attackers overrode branch protection, approved a production release, and published malicious litellm==1.107.0 wheels (~104 minutes live on PyPI 11:39–13:23 UTC Oct 21) plus Docker/GHCR tags v1.107.0 / latest / main-latest / main-stable pointed at a compromised index (Docker Hub until ~14:20 UTC). Malware: credential stealer + remote-code loader (cook.pth / sitecustomize.py). Official GitHub source tag for 1.107.0 did not contain malware — artifacts were built from an attacker-controlled repo. Packages/tags pulled; pin to 1.106.2 or any pre-incident explicit version. Enterprise private registry not impacted. Vendor-confirmed incident report; investigation ongoing.
Highest-severity overnight AI-gateway supply-chain hit — widely deployed LLM proxy; auto-latest Docker and unpinned pip installs at high risk.
More ▾ Less ▴
On Oct 21, 2026, LiteLLM published Contained: Oct 21, 2026 LiteLLM release v1.107.0 Compromised (last updated 16:00 UTC; editor spot-check ~06:00 HKT Thu 22). Stolen GitHub CLI OAuth tokens on three developer accounts let attackers override branch protection, approve a production release, and publish malicious litellm==1.107.0 wheels to PyPI (live ~11:39–13:23 UTC) plus Docker Hub/GHCR tags v1.107.0, latest, main-latest, and main-stable pointing at compromised image indexes (Docker Hub until ~14:20 UTC). Malware includes a credential stealer and remote-code loader via cook.pth / sitecustomize.py. The official GitHub source tag for 1.107.0 did not contain the malware — artifacts were built from an attacker-controlled repo. Packages and tags have been pulled; OSS users should pin to 1.106.2 or any pre-incident explicit version. Enterprise private registry not impacted. Status: incident contained, investigation in progress.
- Root-cause post-mortem and token-theft mechanism
- IoC follow-through / GHSA or CVE numbers
- Whether additional maintainer accounts show residual access
Vendor-confirmed LiteLLM first-party incident post (Oct 21). Editor verified primary URL. Investigation ongoing — do not claim full containment beyond vendor status. Desk did not independently reproduce malware behavior.