LiteLLM Master Key Leak Exposes GitHub Tokens, Enables Malicious Package Hijack

What happened

In May 2026 a LiteLLM configuration file with the platform’s master key was committed to the public LiteLLM‑Labs/lite‑harness repository. Threat actors used the key to retrieve the repository’s GitHub personal access tokens and uploaded a malicious version of the lite‑llm Python package, hijacking the release pipeline.

Why it matters for trust and compliance

• The breach tests the control objective of secure secret management and CI/CD pipeline integrity, a single VCF control that satisfies multiple framework requirements. Continuous monitoring and immutable evidence of secret handling are essential to demonstrate due‑diligence during investigations.
• Shows the need for automated secret‑scanning and continuous evidence collection to prove control effectiveness.
• Provides a concrete audit trail example for demonstrating supply‑chain integrity to regulators and partners.

Who is affected

Recommended actions

1. Rotate all compromised tokens and master keys immediately; enforce short‑lived credentials.
2. Implement automated secret‑detection tools across all code repositories.
3. Restrict CI/CD service‑account permissions to least‑privilege and require multi‑factor approvals for package publishing.
4. Enable immutable logging of repository changes for defensible audit evidence.