Skip to main content
Apexward Pulse
Type Incident

BerriAI LiteLLM

LiteLLM Compromised in Fresh Supply Chain Attack

1 source

At a glance

Low
30-day window, from the last update
Evidence-weighted, not popularity
Why Low

Low rather than Medium: UK relevance is 40 of 100, little UK-specific signal so far.

Briefing

  • Do not treat uncorroborated claims as confirmed breaches.

Questions to ask IT

  • Do we use Litellm, and has anything unusual been seen on it?
  • Would our monitoring spot an attack like this, and who would we call if it did?

Next steps

  1. Confirm whether this affects systems or suppliers in your estate

Summary

  • Hackers used compromised GitHub CLI OAuth tokens to push and approve malicious packages on PyPI and Docker. The post LiteLLM Compromised in Fresh Supply Chain Attack appeared first on SecurityWeek. " ": "Hackers used compromised GitHub CLI OAuth tokens to push and approve malicious packages on PyPI and Docker." " ": "LiteLLM Compromised in Fresh Supply Chain Attack" This website stores cookies on your computer.

Read the original reportSecurityWeek(opens in a new tab)

Products and services involved

Pulse

Last checked 4d ago · Recheck overdue since 6 Nov 2026, 22:34 UK time · 2 quiet checks collapsed

  1. Story23 Oct 2026, 09:17 UK time · 23 Oct

    Linked reporting from SecurityWeek (independent original reporting).

    Read source (SecurityWeek)

1 entry so far. The timeline chart appears once this story has more history.

Sources

How we know

Statements extracted from sources. Higher confidence means stronger corroboration.

  • ClaimedHeadline60% confidence

    LiteLLM Compromised in Fresh Supply Chain Attack

  • ProbableSummary fact75% confidence

    Hackers used compromised GitHub CLI OAuth tokens to push and approve malicious packages on PyPI and Docker. The post LiteLLM Compromised in Fresh Supply Chain Attack appeared first on SecurityWeek. LiteLLM Compromised in Fresh Supply Chain Attack This website stores cookies on your computer.