Latest / Decrypted: The UK Cyber Briefing / The LiteLLM breach that leaked 2,500 companies' secrets, and the dependency nobody pinned
Transcript
- 0:03This is Decrypted. Thursday, the thirteenth of August.
- 0:06The LiteLLM breach that leaked 2,500 companies' secrets, and the dependency nobody pinned.
- 0:14Five months ago, an open-source AI proxy called LiteLLM was quietly poisoned.
- 0:22Now the bill has come due.
- 0:24This week a researcher firm published its analysis of a 153GB archive lifted from the attackers.
- 0:32It holds credentials harvested from roughly 2,500 corporate domains.
- 0:38It's a supply chain story with an AI-shaped twist.
- 0:42And the design failure at its centre is depressingly ordinary.
- 0:47Next. What actually happened.
- 0:51LiteLLM is a widely used gateway.
- 0:55It routes an application's calls to whichever AI model sits behind it.
- 0:59That makes it exactly the kind of infrastructure nobody thinks about until it breaks.
- 1:05In March, attackers calling themselves TeamPCP compromised the build process of Trivy, a popular open-source
- 1:14vulnerability scanner. They rewrote a Git tag to point at a malicious release.
- 1:19LiteLLM's own C I pipeline pulled Trivy without pinning it to a specific, verified version.
- 1:26So the poisoned scanner ran during LiteLLM's build.
- 1:30It quietly exfiltrated the token used to publish packages to PyPI.
- 1:35With that token, the attackers pushed two malicious LiteLLM releases.
- 1:40The second added a file that Python runs automatically on every interpreter startup.
- 1:46That happens whether or not anything actually imports LiteLLM.
- 1:50Any machine that had recently installed the package ran the attacker's code, developer laptop or C I runner a
- 1:58like. Nobody had to open a terminal.
- 2:01For roughly forty minutes, before PyPI pulled the releases, the malware collected secrets from every environ
- 2:08ment it touched. A W S, Azure and Google Cloud credentials.
- 2:13S S H keys. Kubernetes tokens.
- 2:17Slack and Salesforce secrets.
- 2:19It all sat in an attacker's archive until this week.
- 2:23That's when a threat intelligence firm obtained and analysed it.
- 2:27The firm attributed exposed C I runner data to nearly 2,500 corporate domains, including Samsung, Cisco, Sale
- 2:36sforce and Siemens.
- 2:39The Secure by Design lesson.
- 2:42Nothing about this attack was exotic.
- 2:45It worked because of two ordinary, avoidable choices.
- 2:48First, a build pipeline that trusted a third-party tool without pinning its version.
- 2:54Second, a publishing token with no scoping or short expiry, sitting in a runner that also ran untrusted code.
- 3:03So pin your dependencies. Yes, including the security scanner you installed specifically to catch this kind
- 3:10of thing. And treat any token that can publish to the world as a secret.
- 3:15It should live nowhere near a general-purpose build step.
- 3:19LiteLLM's maintainers have since rebuilt their pipeline around isolated environments with tighter gates.
- 3:25That's the right fix. It's just five months late for the organisations whose secrets were already in that arc
- 3:32hive by the time it shipped.
- 3:33For UK organisations, the lesson isn't really about LiteLLM.
- 3:38A huge amount of your C I and C D estate runs software you didn't write.
- 3:43It's updated by a process you don't control.
- 3:46And it holds credentials that would let an attacker move sideways into cloud accounts and customer systems.
- 3:52So treat your build pipeline with the same scepticism you'd apply to a stranger asking for your A W S keys.
- 3:59Because that is functionally what an unpinned dependency is.
- 4:03That was Decrypted. The written version and every source are linked in the show notes.
- 4:09Thanks for listening.