npm package report

Is color-convert safe?

Version 3.1.1 of color-convert was compromised. Other versions are not flagged as malicious.

Do not install color-convert 3.1.1

CRITICAL

Compromised releases. Added to CyberXYZ 2025-09-08, OSV malicious-package feed (Google / OpenSSF).

// what we observed

The package was compromised and malicious code added. Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Reported by GitHub Advisory Database via OSV.

// versions and what to do
Malicious
3.1.1
Move to
3.1.3 newest 3.x release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install color-convert@3.1.3

OSV recordreferenceadvisoryissueadvisoryadvisory

// reach

1 direct dependencies

1 carry known advisories, worst HIGH

30 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade
// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.


cvss
8.8
high

CVSS v4.0 base score out of 10

epss
0.43%
medium

chance of exploitation in 30 days, 37th percentile of all CVEs

xyz score
4.5
medium

CyberXYZ composite out of 10

fig. 01 — GHSA-pxx3-g568-hxr4, the advisory selected below

// 1 advisories

GHSA-pxx3-g568-hxr4

HIGHGitHub ratingCVE-2025-59162
// impact

On 8 September 2025, the npm publishing account for color-convert was taken over after a phishing attack. Version 3.1.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.

// patches

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. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.

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.

// references// point of contact

In the event suspicious behavior is still observed for the package listed in this security advisory after performing all of the above cleaning operations (see Patches above), please reach out via one of the following channels of communication:

// cvss v4.0 vector

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

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
High
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None
Exploit maturity
Attacked
U
Red

Checked 2026-11-06 at 21:51 UTC. The most recent advisory here was published 2025-09-15. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.