LiteLLM 1.107.0 was compromised: the release shipped credential-stealing malware
LiteLLM's incident report says litellm 1.107.0 was live on PyPI for about two hours on October 21, and its Docker images, including latest, were compromised the same day. It contained compiled malware that steals credentials and loads remote-code execution tools. LiteLLM says anyone who installed or ran it should assume the system is compromised, pin 1.106.2 and rotate every secret the host could reach.
What it means for yourotate every key that host could reach, from a clean machine, as Datadog advises. LiteLLM says its private enterprise release wasn't affected.
With Henry, AI safety analyst. Hosted by Aiden.
Sources
- LiteLLM: Contained: Oct 21, 2026 LiteLLM release v1.107.0 Compromised docs.litellm.ai, Oct 21, 2026
- LiteLLM: v1.107.0 security incident, attack chain docs.litellm.ai, Oct 23, 2026
- Datadog Security Labs: LiteLLM compromised on PyPI and Docker securitylabs.datadoghq.com, Oct 21, 2026
Read the transcript
AidenInstalled LiteLLM 1.107.0 or its affected Docker images? LiteLLM says to assume it's compromised.
AidenHenry, our AI safety analyst. What happened, and what do you do now?
HenryLiteLLM says its release pipeline was compromised on October 21. That version was on PyPI for about 2 hours, with Docker tags including latest. It carried malware that steals credentials and loads remote code execution tools.
AidenDatadog Security Labs counts about 23 million weekly downloads. Is removing the package enough?
HenryNo. Datadog says the malware runs whenever Python starts, and its dropped files survive. LiteLLM's report lists them: delete them first, then reinstall pinned to 1.106.2.
AidenSo, for you: rotate every key that host could reach, from a clean machine, as Datadog advises. LiteLLM says its private enterprise release wasn't affected.
AidenDailyChat is AI-generated. Aiden and Henry are AI characters, not real experts. Facts come from the sources we link. Not professional advice. See you tomorrow.
