Leaked key to an internal agent platform leads to a malicious LiteLLM release
An attacker used a leaked key to LiteLLM’s internal agent platform to obtain an organization owner’s GitHub token, then rewired the release workflow to publish a credential stealer as litellm 1.107.0.
- Occurred
- Disclosed
- Published
- Updated
- Organization
- LiteLLM (BerriAI)
- System
- LiteLLM AI gateway (PyPI and Docker images) and the internal LiteLLM Agent Platform
- Impact
- Credential-stealing litellm 1.107.0 live on PyPI for about two hours and on Docker Hub for about two and a half hours
- Root cause
- An unrevoked admin key to an internal agent platform exposed the GitHub token of an organization owner
Timeline
- 2026-05-27. A configuration file with an admin key to the internal LiteLLM Agent Platform is committed to a public repository. It is deleted about three hours later, but the key is not revoked.
- 2026-10-10. The attacker uses the key and obtains an organization owner’s GitHub CLI token, then runs workflows that send CI secrets to an outside endpoint.
- 2026-10-21, 11:39 UTC. litellm 1.107.0 is published to PyPI. Docker images follow at 11:46.
- 2026-10-21, by 13:23 UTC. PyPI quarantines the package. Docker Hub tags are cleaned by 14:20.
- 2026-10-23. LiteLLM publishes its root cause analysis.
Trigger or entry point
The leaked admin key. LiteLLM describes the Agent Platform as an experimental service for self-hosted cloud agents that file pull requests to GitHub repositories.
Failure mechanism
According to LiteLLM, the platform was configured with the GitHub CLI OAuth token of an organization owner rather than a scoped token, and its API returned that token in agent configurations. With owner rights, the attacker overrode branch protection and changed the release workflow to build from a lookalike fork. Tokens of two other maintainers, taken from CI secrets that the attacker’s workflows had sent out, were used to approve the release and then delete the run records. Earlier that week, the release gate had been relaxed so that any two engineers could trigger and approve a release, according to LiteLLM.
LiteLLM’s first post said the tokens were taken from the logs of an internal LiteLLM deployment. Its later analysis found that the owner’s token came from the Agent Platform’s API response.
Impact
The release carried malware that steals credentials and loads remote code, according to LiteLLM. The Register reports that it targeted browser, cloud and LLM provider credentials. LiteLLM tells anyone who ran it to treat the environment as compromised. Enterprise customers on the private registry were not affected.
Response
LiteLLM removed the artifacts, locked its registries, removed all members from its GitHub organization except one trusted account, and is revoking every token across its systems.
Mitigations
LiteLLM rotated its image signing key on October 23. Since November 15, releases are signed with keyless cosign instead of a stored key. LiteLLM believes the old key was exposed, and the compromised 1.107.0 images carry a valid signature from it.
Engineering takeaway
- Failure pattern
- An agent platform that only needed to open pull requests held an unscoped token of a GitHub organization owner, and its own admin key had leaked.
- Preventive control
- Give agent platforms fine-grained tokens limited to the repositories and actions they need, and revoke any key that reaches a public repository at once.
- Transferable lesson
- A credential stored for an agent is reachable by anyone who reaches the agent platform.
Editorial summary by Incidents.si, drawn from the sourced record above. It is not a statement by the organizations involved.
Sources
- Contained: Oct 21, 2026 LiteLLM release v1.107.0 Compromisedprimary · 2026-10-21
- The attack chain behind the v1.107.0 LiteLLM releaseprimary · 2026-10-23
- LiteLLM supply chain attack hoovers up passwords and secretssecondary · 2026-10-21
Corrections
- Review against the sources on the day of publication. Corrected what LiteLLM’s first post said about where the tokens came from, and added how the other two maintainers’ tokens were obtained.2026-11-20