Skip to main content
Back to Situations
developingCyber

LiteLLM Supply Chain Attack via Compromised GitHub OAuth Tokens

The LiteLLM project's release pipeline was compromised via attackers utilizing compromised GitHub CLI OAuth tokens.

AI disclosure: Model-written assessment of the linked reports, not a verified fact. Check the sources. How Mosaic works

Reported3 of 6 key facts linked
Not measuredno reporting-volume measure is served for situations
Not assessedno severity is rated for situations
2 publishers2 reports

: Stable (the model's assessment, not a measurement)

Oct 23First seen Oct 23Assessment written Oct 23
Why now
Newest report Oct 23: LiteLLM hit by supply chain attack via compromised GitHub OAuth tokens (SecurityWeek).from the newest member report, published 23 Oct 08:10 UTC
Why it matters
This incident underscores the escalating risk of supply chain attacks targeting critical AI infrastructure and developer tooling ecosystems.
Affected
No country is recorded for this situation.countries named in the evidence; the lead is the country it is filed under, not an event location
Next catalyst
No scheduled catalyst known.Mosaic holds a schedule only for economic-calendar releases; 3 indicators to watch below
Watch in Monitor Export brief

Save keeps it in Monitor › Saved, without alerts. Watch opens Monitor with “AI Supply Chain Attack” as the subject.

Known and unknown

key facts by their own evidence status

Known

  • ReportedLiteLLM project's release pipeline was compromised.
  • ReportedMalicious PyPI packages and Docker images were distributed.
  • ReportedMalicious artifacts exfiltrate credentials, secrets, and environment variables.

Not established

  • Attackers used compromised GitHub CLI OAuth tokens.
  • Full scope of affected users and packages.
  • Full duration of the intrusion.

stated, not yet supported by linked evidence

Indicators to watch

  • →Official statements from LiteLLM or GitHub regarding remediation and impact.
  • →Analysis of the specific info-stealer malware's capabilities and targets.
  • →Reports of other projects or users affected by similar GitHub OAuth token compromises.

what would change the read; not a schedule

Evidence

Reported · 2 signals · 2 distinct outlets

Central claim LiteLLM hit by supply chain attack via compromised GitHub OAuth tokens

Reported2 · 2 src · best source record low

Timeline

first seen 23 Oct 08:20 UTC · 2 timed reports · published time, else recorded

Connected

named in this situation's reports; not a claim that one causes another

Other situations

No country is recorded, so there is no place to match on.

Actors

Loading…

Places

No country is recorded for this situation.

Anomalies

Loading…

Assessment

model confidence: under Technical details
Read the full assessment

The LiteLLM project's release pipeline was compromised via attackers utilizing compromised GitHub CLI OAuth tokens. This enabled the publication of malicious PyPI packages and Docker images designed to exfiltrate credentials, secrets, and environment variables. The full scope of affected users and the duration of the intrusion remain under assessment.

AI disclosure: Model-written assessment of the linked reports, not a verified fact. Check the sources. How Mosaic works

Topics supply-chain · github · pypi · docker · ai · open-source · malware · ai-tools · credential-theft

Technical details
Impact score
5.0 / 10 · a priority score, not confidence
Model confidence
Medium: evidence reported (3 of 6 key facts linked to evidence; the model marked a key fact as unclear); 2 distinct outlets
Coverage focus
100% in primary evidence group
Coherence
0.90
Review state
published
Refreshed
Updated Oct 23, synthesized Oct 23. Not evidence time.
Cluster type
story
Member signals
2
Situation id
3aaa14fb-9a14-4ba6-85a7-528e5c612b24
Last evidenceOct 23, 08:18 UTC
Last successful evaluationSuccessful evaluation timestamp unavailable (legacy)
Last attempt·

Discussion

…

Sign in to add a note, contribute a source, or challenge the assessment.