LiteLLM traces supply chain attack to a GitHub key nobody revoked

LiteLLM has traced its latest supply chain attack to a mistake made months earlier. According to the project’s postmortem, a master key exposed on GitHub was never revoked, and an attacker eventually used it to poison an official software release. The gap between the leak and the payoff was roughly five months. That is a long time for a door to sit unlocked, and it shows that attackers are patient. How the attack unfolded LiteLLM is an open-source Python library that acts as a router for AI models. Think of it as a universal remote: one interface that sends requests to multiple large language model providers, so developers do not have to wire up each one separately. The trouble started on May 27, 2026. A master key from an earlier experimental deployment was accidentally committed to a public repository. The key was never revoked, and it stayed active for 136 days. On October 10, an attacker put it to use. The intruder extracted sensitive tokens, including a GitHub CLI OAuth token, which opened the path to tampering with the repository’s CI workflows. CI workflows are the automated pipelines that build and publish software. Control those, and you can ship code that carries the proj...