LiteLLM discloses intrusion details: leaked key not revoked, ultimately leading to backdooring of release
LiteLLM published an investigation into the attack chain involved in the backdooring of the v1.107.0 release, and researcher Johann Rehberger summarized several key points. The key used to backdoor LiteLLM was accidentally leaked on May 27, 2026; the leak was discovered internally, but the key was never revoked, and the author says the attacker appears to have obtained it as well. On October 10, the attacker used the key to further gain GitHub credential access, ultimately breaching LiteLLM's release process and implanting a backdoor. More than 4 months passed from the key leak to its exploitation.
More than four months passed from the key leak to the backdooring of the release, and teams relying on LiteLLM can use this to review weak points in credential management and the release pipeline.
Recent LiteLLM compromise details
- Key used to backdoor LiteLLM was accidentally leaked on May 27, 2026
- the leak was discovered internally, but key was never revoked! Seems attacker got hold of it too
- On October 10, the attacker exploited it, gained further access to GitHub creds, and ultimately backdoored LiteLLM releases
More than 4 months between exposure and exploitation
We have completed our investigation into the attack chain behind the v1.107.0 release. Read it here: https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chainView the quoted post on X