<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Python-Package on CuraSec</title><link>https://curasec.metacog.co.kr/tags/python-package/</link><description>Recent content in Python-Package on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Oct 2026 15:52:23 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/python-package/index.xml" rel="self" type="application/rss+xml"/><item><title>LiteLLM Supply Chain Compromise Pushes Credential Stealer to PyPI and Docker Hub</title><link>https://curasec.metacog.co.kr/insights/2026-10-22-litellm-suspects-github-token-leak-in-ai-gateway-logs-behind/</link><pubDate>Thu, 22 Oct 2026 15:52:23 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-22-litellm-suspects-github-token-leak-in-ai-gateway-logs-behind/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Active supply chain compromise: if you run litellm, check immediately for version 1.107.0 in pip environments and Docker images, remove it, rotate any credentials and LLM API keys that may have been exposed through the credential stealer.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Sweep all systems for litellm==1.107.0 installations deployed on or after October 21, 2026; hunt for outbound connections or credential exfiltration from hosts where that version ran, and treat any match as a potential backdoor compromise.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> LiteLLM is widely used as an AI gateway routing LLM API keys — confirm whether any teams use it, check exposure to the malicious 1.107.0 release, and request LiteLLM&amp;rsquo;s incident report to assess scope before this surfaces in board-level AI security discussions.&lt;/li>
&lt;/ul></description></item></channel></rss>