CVE-2025-59145 [email protected] contains malware after npm account takeover
Attackers injected malware into a popular npm package to hijack cryptocurrency transactions in browser environments, requiring users to rebuild bundles.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-59145?
CVE-2025-59145 is a high-severity vulnerability in colorjs color-name, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
color-name is a JSON with CSS color names. On 8 September 2025, an npm publishing account for color-name was taken over after a phishing attack. Version 2.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'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 2.0.2.
Weakness: CWE-506
Which versions are affected by CVE-2025-59145?
How do I fix CVE-2025-59145?
Upgrade to a fixed version.
Is CVE-2025-59145 being exploited?
There is no known exploitation of CVE-2025-59145 in the wild and no public exploit code.