← All stories

Threat intel

Leaked LiteLLM Master Key Let Attackers Steal GitHub Tokens and Hijack Release Pipeline

LiteLLM disclosed that a master key accidentally committed to a public GitHub repository in late May 2026 let a threat actor steal GitHub tokens, hijack its release pipeline and push a malicious version of the popular Python package, according to The Hacker News.

Cover for a threat-intel story

LiteLLM has disclosed that a master key accidentally published to a public GitHub repository in late May 2026 allowed a threat actor to steal GitHub tokens, hijack its release pipeline and ultimately push a malicious version of the popular Python package, according to The Hacker News.

In its disclosure on Friday, the project said that on May 27, 2026, a configuration file was committed to the public LiteLLM-Labs/lite-harness repository that inadvertently contained the master key to an Agent Platform deployment. Possession of that key gave the attacker access that was subsequently abused to obtain GitHub tokens and take control of the release process, the report said.

The incident turned a single exposed credential into a supply chain compromise: with control of the release pipeline, the threat actor was able to publish a tampered version of the package to downstream users. Because the package is widely used in the Python ecosystem, the hijack raised the risk that developers and organizations pulling the malicious release could have been exposed.

Details such as how long the malicious version remained available, how many users may have been affected, and what steps LiteLLM took to revoke the key and secure its pipeline were not included in the material available to this newsroom. The Hacker News reported that the disclosure was made by LiteLLM itself on Friday.

Source: The Hacker News

How to read this

Authorized-only · evidence-based · point-in-time. Aegis cannot guarantee the absence of weaknesses or hidden devices. On this machine, live external HTTP/TLS may be network-blocked and shown as an honest coverage gap. Severity and confidence are kept separate. Finished assessments persist in the encrypted store while durable storage is bound. A theme choice may persist in this browser. Export remains available for a copy you can take with you.