Skip to content

Back to the catalog

Dark Web Intelligence (@DailyDarkWeb) on X
x.comthread

Dark Web Intelligence (@DailyDarkWeb) on X

LiteLLM suspects its October 21 release compromise began with Claude Code responses containing GitHub CLI OAuth tokens that were written to logs of an internet-facing internal LiteLLM gateway. Attackers allegedly stole those tokens, used an organization-owner token to disable branch protections, and pushed poisoned artifacts from a lookalike repository. How they entered the gateway is unconfirmed, and this is not a proven Claude Code vulnerability.

TL;DR LiteLLM suspects leaked GitHub OAuth tokens in AI-gateway logs let attackers hijack its release workflow in the October 21 compromise.
Open original ↗

Organisations named here

  • LiteLLM release compromise
  • lookalike repository

Technologies named here

  • LiteLLM
  • Claude Code
  • LiteLLM AI gateway logs
  • GitHub CLI OAuth tokens
  • GitHub CLI
  • GitHub organization-owner token
  • GitHub
  • OAuth

Techniques named here

  • Theft of credentials from AI-gateway logs, suspected
  • Hijacking of the release workflow
  • Poisoned artifacts supplied from a lookalike repository
  • Software supply chain compromise
  • Branch protection bypass

Related in Supply Chain