<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[LiteLLM Suspects GitHub Token Leak in AI Gateway Logs Behind Malicious Package Release]]></title><description><![CDATA[<p dir="auto"><strong>LiteLLM</strong> has disclosed that attackers compromised <strong>multiple independent security controls</strong> in order to publish a malicious version of its Python package, which bundled a credential stealer and a backdoor.</p>
<p dir="auto">The compromise of LiteLLM's release pipeline occurred on <strong>October 21, 2026</strong>, at approximately <strong>4:00 a.m.</strong>, when a malicious build was pushed as version <strong>1.107.0</strong> to both the <strong>Docker Hub</strong> registry and the <strong>Python Package Index (PyPI)</strong>.</p>
<p dir="auto">The company suspects that a leaked <strong>GitHub token</strong>, possibly exposed through AI gateway logs, played a role in the breach. The incident is notable because it required bypassing several separate safeguards rather than exploiting a single weak point.</p>
<ul>
<li>The malicious release was published as version <strong>1.107.0</strong></li>
<li>Distribution channels affected: <strong>Docker Hub</strong> and <strong>PyPI</strong></li>
<li>The package contained both a <strong>credential stealer</strong> and a <strong>backdoor</strong></li>
</ul>
<p dir="auto">Users who installed or pulled LiteLLM version <strong>1.107.0</strong> from either channel around the time of the incident should treat any credentials accessible to that environment as potentially exposed and rotate them as a precaution.</p>
<p dir="auto">Source: <a href="https://thehackernews.com/2026/10/litellm-suspects-github-token-leak-in.html" target="_blank" rel="noopener noreferrer nofollow ugc">The Hacker News</a></p>
<p dir="auto">Did your organization pull LiteLLM <strong>1.107.0</strong> from PyPI or Docker Hub, and if so, what steps are you taking to verify and rotate exposed credentials?</p>
]]></description><link>https://xploitlk.com/topic/786/litellm-suspects-github-token-leak-in-ai-gateway-logs-behind-malicious-package-release</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 07:22:32 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/786.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 25 Oct 2026 10:30:18 GMT</pubDate><ttl>60</ttl></channel></rss>