Skip to main content
CVE-2025-59331VulnerabilityPublished

CVE-2025-59331: Qix- node-is-arrayish · Embedded Malicious Code

Affects Qix- node-is-arrayishSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in 0.3.4 : patch Qix- node-is-arrayish soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.3.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:A/U:Red

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Qix- node-is-arrayishAffected
  • =0.3.3
Fixed in–

AI-suggested

European organizations should immediately audit their projects for usage of 'node-is-arrayish' version 0.3.3 or earlier vulnerable versions. They must upgrade to version 0.3.4 or later without delay. Complete removal of the node_modules directory and clearing of all package manager caches (npm, yarn, pnpm, etc.) is essential to prevent residual compromised code. All browser bundles that include this package must be rebuilt from scratch to ensure the malicious payload is eliminated. Organizations operating private npm registries or mirrors should purge any cached copies of the compromised version 0.3.3 to prevent inadvertent reuse. Implementing strict supply chain security practices, such as verifying package integrity via checksums or signatures, and enabling two-factor authentication on publishing accounts can reduce the risk of similar account takeovers. Monitoring for unusual cryptocurrency transaction patterns in browser environments and educating developers about phishing risks are also recommended. Finally, integrating automated dependency scanning tools that flag compromised or malicious packages can help detect and prevent future incidents.

Description

is-arrayish checks if an object can be used like an Array. 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. Local environments, server environments, command line applications, etc.are not affected. If the package was used in a browser context (e.g.a direct <script> 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. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. 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. 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. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue is resolved in 0.3.4.

References

Community reviews

Loading reviews…