Status: Incident contained, investigation located here
Last updated: October 21, 2026 20:30 UTC
In the early morning of October 21, LiteLLM's release pipeline was compromised
and pushed v1.107.0 to the docker registry and PyPi. This version contained
compiled malware which steals credentials and loads remote-code execution tools.
All previous versions are safe, and the impacted releases have been pulled.
Enterprise Customers running the private enterprise release of LiteLLM were not impacted.
Update (20:30 UTC): We believe we have identified the attack chain which facilitated this attack. The attacker had to compromise multiple independent security controls to be successful. See How this happened below.
Update (October 23, 21:50 UTC): This post was written while our investigation was ongoing. Some our assumptions and beliefs reflected in our status updates and the text below were later discovered to be inaccurate or incomplete. We have left them in their original form as a record of our investigation, but have posted a canonical record here.
Update (October 30): The commit that rotated our cosign image signing key on October 23 now shows as verified on GitHub, and we added the new key's fingerprint to this post. See Image signing key rotation.
Update (November 15): Releases are now signed with keyless cosign instead of a stored key, starting with v1.111.0-dev.3. See Keyless signing.