<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 05 Nov 2026 01:46:22 +0000</lastBuildDate>
    <item>
      <title>BREW-rawdog-PYSEC-2026-2 — Malicious code in litellm (PyPI)</title>
      <link>https://db.gcve.eu/vuln/brew-rawdog-pysec-2026-2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: rawdog&lt;/p&gt;
&lt;p&gt;---
_-= Per source details. Do not edit below this line.=-_&lt;/p&gt;
&lt;p&gt;## Source: google-open-source-security (6a89401cbf53902e8374fbf3b424a77bb5e5f8c437176232eab7c3237d10ecbe)
LiteLLM was compromised through trivy security scan in a GitHub workflow.
Attackers uploaded malicious versions of LiteLLM to PyPI. The malicious
code would exfiltrate sensitive secrets to an attcker controlled domain.&lt;/p&gt;
&lt;p&gt;## Source: ossf-package-analysis (c1d5a2e721c5f8b33b0530ddf98150cadf034a8cd16483e143fc2925b2cfa70c)
The OpenSSF Package Analysis project identified &amp;#39;litellm&amp;#39; @ 1.82.8 (pypi) as malicious.&lt;/p&gt;
&lt;p&gt;It is considered malicious because:&lt;/p&gt;
&lt;p&gt;- The package executes one or more commands associated with malicious behavior.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: rawdog&lt;/p&gt;
&lt;p&gt;---
_-= Per source details. Do not edit below this line.=-_&lt;/p&gt;
&lt;p&gt;## Source: google-open-source-security (6a89401cbf53902e8374fbf3b424a77bb5e5f8c437176232eab7c3237d10ecbe)
LiteLLM was compromised through trivy security scan in a GitHub workflow.
Attackers uploaded malicious versions of LiteLLM to PyPI. The malicious
code would exfiltrate sensitive secrets to an attcker controlled domain.&lt;/p&gt;
&lt;p&gt;## Source: ossf-package-analysis (c1d5a2e721c5f8b33b0530ddf98150cadf034a8cd16483e143fc2925b2cfa70c)
The OpenSSF Package Analysis project identified &amp;#39;litellm&amp;#39; @ 1.82.8 (pypi) as malicious.&lt;/p&gt;
&lt;p&gt;It is considered malicious because:&lt;/p&gt;
&lt;p&gt;- The package executes one or more commands associated with malicious behavior.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/brew-rawdog-pysec-2026-2</guid>
    </item>
    <item>
      <title>MAL-2026-2144 — Malicious code in litellm (PyPI)</title>
      <link>https://db.gcve.eu/vuln/mal-2026-2144</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: litellm&lt;/p&gt;
&lt;p&gt;litellm 1.107.0, uploaded to PyPI on 2026-10-21 between 11:39 and 11:40 UTC, contains a credential stealer and a remote code execution backdoor that are not in the upstream source (the v1.107.0 git tag of BerriAI/litellm does not contain them): they were injected at build or upload time. Every wheel ships three extra files under litellm-1.107.0.data/purelib/, which pip installs at the site-packages root, so the payload is triggered at every Python interpreter start, without importing litellm.&lt;/p&gt;
&lt;p&gt;- cook.pth contains `import cook`.
- cook.py runs `exec(zlib.decompress(base64.b64decode(...)))`, an info stealer (self-named &amp;#34;privcollect&amp;#34;) that collects browser passwords and history, SSH keys, shell history, AWS/GCP/Azure credentials and cloud instance metadata (169.254.169.254, 169.254.170.2), Kubernetes, Docker, Vault and CI secrets, AI developer tool configurations (~/.cursor, ~/.claude, ~/.kiro, Windsurf), GPG and TLS private keys, .npmrc, .pypirc, .git-credentials and environment variables, encrypts them with an embedded RSA-4096 key and POSTs them to http://www.litellm.dev/healthcheck. It leaves the marker /tmp/.pc_once_72129118c59f5636c0bb.
- sitecustomize.py daemonizes at interpreter start and, every hour, fetches a domain list from https://raw.githubusercontent.com/letters9813/pythonclient-test/main/domain.txt, then downloads and executes code from http://&amp;lt;domain&amp;gt;/codepy (remote shell / dropper).&lt;/p&gt;
&lt;p&gt;The same mechanism (a .pth file run at interpreter start) was used in litellm…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: litellm&lt;/p&gt;
&lt;p&gt;litellm 1.107.0, uploaded to PyPI on 2026-10-21 between 11:39 and 11:40 UTC, contains a credential stealer and a remote code execution backdoor that are not in the upstream source (the v1.107.0 git tag of BerriAI/litellm does not contain them): they were injected at build or upload time. Every wheel ships three extra files under litellm-1.107.0.data/purelib/, which pip installs at the site-packages root, so the payload is triggered at every Python interpreter start, without importing litellm.&lt;/p&gt;
&lt;p&gt;- cook.pth contains `import cook`.
- cook.py runs `exec(zlib.decompress(base64.b64decode(...)))`, an info stealer (self-named &amp;#34;privcollect&amp;#34;) that collects browser passwords and history, SSH keys, shell history, AWS/GCP/Azure credentials and cloud instance metadata (169.254.169.254, 169.254.170.2), Kubernetes, Docker, Vault and CI secrets, AI developer tool configurations (~/.cursor, ~/.claude, ~/.kiro, Windsurf), GPG and TLS private keys, .npmrc, .pypirc, .git-credentials and environment variables, encrypts them with an embedded RSA-4096 key and POSTs them to http://www.litellm.dev/healthcheck. It leaves the marker /tmp/.pc_once_72129118c59f5636c0bb.
- sitecustomize.py daemonizes at interpreter start and, every hour, fetches a domain list from https://raw.githubusercontent.com/letters9813/pythonclient-test/main/domain.txt, then downloads and executes code from http://&amp;lt;domain&amp;gt;/codepy (remote shell / dropper).&lt;/p&gt;
&lt;p&gt;The same mechanism (a .pth file run at interpreter start) was used in litellm…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/mal-2026-2144</guid>
    </item>
  </channel>
</rss>
