<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T08:22:36.106505+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-frh7-2f84-v9mw</id>
    <title>GHSA-frh7-2f84-v9mw — is-arrayish@0.3.3 contains malware after npm account takeover</title>
    <updated>2026-10-07T08:22:36.107974+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: is-arrayish</p>
<p>### Impact
On 8 September 2025, an npm publishing account for `is-arrayish` was taken over after a phishing attack. Version `0.3.3` was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments.</p>
<p>Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct `&lt;script&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.</p>
<p>The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.</p>
<p>### Patches
npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.</p>
<p>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.</p>
<p>Users should update to the latest patch version, completely remove their `node_modules` directory, clean their package manager's global cache, and rebuild any browser bundles from scratch.</p>
<p>Those operating…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-frh7-2f84-v9mw"/>
  </entry>
</feed>
