<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 14:39:12 +0000</lastBuildDate>
    <item>
      <title>GHSA-qrmh-qg46-72pp — color@5.0.1 contains malware after npm account takeover</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qrmh-qg46-72pp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: color&lt;/p&gt;
&lt;p&gt;### Impact
On 8 September 2025, the npm publishing account for `color` was taken over after a phishing attack. Version `5.0.1` was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker&amp;#39;s own addresses from within browser environments.&lt;/p&gt;
&lt;p&gt;Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct `&amp;lt;script&amp;gt;` inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt.&lt;/p&gt;
&lt;p&gt;The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.&lt;/p&gt;
&lt;p&gt;### Patches
npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.&lt;/p&gt;
&lt;p&gt;On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.&lt;/p&gt;
&lt;p&gt;Users should update to the latest patch version, completely remove their `node_modules` directory, clean their package manager&amp;#39;s global cache, and rebuild any browser bundles from scratch.&lt;/p&gt;
&lt;p&gt;Those operating priv…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: color&lt;/p&gt;
&lt;p&gt;### Impact
On 8 September 2025, the npm publishing account for `color` was taken over after a phishing attack. Version `5.0.1` was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker&amp;#39;s own addresses from within browser environments.&lt;/p&gt;
&lt;p&gt;Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct `&amp;lt;script&amp;gt;` inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt.&lt;/p&gt;
&lt;p&gt;The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.&lt;/p&gt;
&lt;p&gt;### Patches
npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.&lt;/p&gt;
&lt;p&gt;On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.&lt;/p&gt;
&lt;p&gt;Users should update to the latest patch version, completely remove their `node_modules` directory, clean their package manager&amp;#39;s global cache, and rebuild any browser bundles from scratch.&lt;/p&gt;
&lt;p&gt;Those operating priv…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qrmh-qg46-72pp</guid>
    </item>
  </channel>
</rss>
