Incident report · Supply chain
Leaked LiteLLM Master Key Let Attackers Steal GitHub Tokens and Hijack Release Pipeline
LiteLLM disclosed that an Agent Platform master key was accidentally published to a public GitHub repository on May 27, 2026. This exposure allowed an attacker to steal GitHub tokens and push a malicious version of the LiteLLM Python package. The incident compromised the integrity of LiteLLM's software supply chain. The key remained public for an unspecified period.
- Discovered
- Oct 23 2026
- Failure mode
- Supply chain
- Source
- The Hacker News · Oct 24 2026
- Impact
- Compromised LiteLLM's release pipeline and allowed distribution of malicious package versions.
Summary from the public record. The failure mode’s analysis follows.
The agent was fine. Everything it trusted was not.
How Fencio prevents this
The agent trusted a component it had never verified: a package, an extension, a skill, or a server that looked legitimate. When that component changed or was compromised, the agent carried the payload straight into a trusted environment.
Fencio inventories every tool, server, and skill an agent can reach, pins their versions and declared capabilities, and blocks calls when a component starts doing something its manifest never declared, like reading env files or mailing new recipients.
Runtime policy example · Supply chainLive
- 16:01:19mcp.tool upload_file(.env)Capability not in pinned manifestBlock
- 16:04:36mcp.tool lint(src/)Manifest match · v1.4.2Allow
- 16:07:53pkg.install(unverified-name)Package not in approved registryBlock
Say yes to the AI your business wants.
Book a 30-minute call. Bring your agents and your rules.