<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PyPI on GMO Flatt Security Research</title>
    <link>https://flatt.tech/research/tags/pypi/</link>
    <description>Recent content in PyPI on GMO Flatt Security Research</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://flatt.tech/research/tags/pypi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Software Supply Chain Attack on LiteLLM: Overview and Response Guidance</title>
      <link>https://flatt.tech/research/posts/litellm-pypi-supply-chain-attack/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/litellm-pypi-supply-chain-attack/</guid>
      <description>&lt;p&gt;Note) This post is a direct translation of &lt;a href=&#34;https://blog.flatt.tech/entry/litellm_2nd_compromise&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;this post&lt;/a&gt;&#xA;.&lt;/p&gt;&#xA;&lt;p&gt;On October 21, 2026, malicious code was injected into the PyPI package &lt;code&gt;litellm&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This article goes into detail on this malicious package based on information we observed and analyzed on the analysis infrastructure behind Takumi Guard, focusing on its impact as well as the countermeasures to take.&lt;/p&gt;&#xA;&lt;p&gt;The purpose of this article is to help readers understand the situation and respond; it is not intended to assist or encourage any illegal activity.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
