All Radar picks

X OPPORTUNITY RADAR / THE BRIEF

The malware passed the approval meeting

LiteLLM's corrected investigation traces its poisoned release to an exposed key that was never revoked—not the log-leak theory in its first account.

Information Overload
2 min readSources
A mechanical stamp approves software parcels beneath an exposed key, while a forked conveyor carries checked and skull-marked boxes, in orange, turquoise and cream.
AI-generated conceptual editorial illustration, not documentary evidence.

A signature can tell you who shipped the parcel, droogs. It cannot promise the parcel isn't a brick aimed at your gulliver.

The correction matters

LiteLLM's October 23 investigation revises its explanation for the malicious version 1.107.0 released on October 21. The company says an Agent Platform master key accidentally entered a public repository on May 27. The commit disappeared; the key was never revoked.[1]

According to LiteLLM, an attacker used it on October 10 to obtain a GitHub organization owner's token, then acquired other maintainers' credentials. Owner privileges overrode release protections. Stolen identities supplied the trigger and approval for a build drawn from a lookalike repository.[1]

The earlier suspicion that the first token came from an internal LiteLLM deployment's logs is superseded. The company now identifies a different service. Repeating the first explanation would preserve the wrong failure story.[1]

Two approvals. One intruder.

Socket independently recovered secret-stealing workflows from October 10 and 12, placing malicious repository activity eleven days before the poisoned release. Its evidence has limits: a workflow reporting success does not itself prove the collector received secrets. The connection between a stolen token and release approval comes from LiteLLM's audit account.[2]

The malicious PyPI release and affected container artifacts were removed on October 21, LiteLLM says. Its official GitHub source tag did not contain the malware; the distributed build came from elsewhere. This is not a claim that every installation—or today's download—is compromised.[3]

Our takeaway: counting approvers is not the same as separating authority. If one compromised identity can dismantle the boundary, the second rubber stamp is office theatre with a very expensive ticket.

FOLLOW THE SOURCES.

Checked Oct 24, 2026. Numbered references point to the evidence behind factual passages. Commentary is our own.

  1. The attack chain behind the v1.107.0 LiteLLM release (opens in a new tab)LiteLLMBack to cited passage
  2. New Evidence Shows LiteLLM Secret-Stealing Workflows Ran 11 Days Before Supply Chain Attack (opens in a new tab)Socket / Karlo ZankiBack to cited passage
  3. Contained: Oct 21, 2026 LiteLLM release v1.107.0 Compromised (opens in a new tab)LiteLLMBack to cited passage
CybersecuritySoftware supply chainAI securityLiteLLMSocket
Back to the latest picks