How severe is GHSA-qrmh-qg46-72pp?

No CVSS score has been assigned to GHSA-qrmh-qg46-72pp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qrmh-qg46-72pp?

GHSA-qrmh-qg46-72pp affects the following packages: color (npm). Ecosystems affected: npm.

How do I fix GHSA-qrmh-qg46-72pp?

Update color to 5.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qrmh-qg46-72pp is resolved across your whole dependency graph.

How do I detect GHSA-qrmh-qg46-72pp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for color, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qrmh-qg46-72pp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-qrmh-qg46-72pp actively exploited in the wild?

No public exploit code has been indexed for GHSA-qrmh-qg46-72pp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-qrmh-qg46-72pp?

GHSA-qrmh-qg46-72pp has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qrmh-qg46-72pp?

GHSA-qrmh-qg46-72pp is classified as CWE-506 (CWE-506). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qrmh-qg46-72pp published, and has it been updated?

GHSA-qrmh-qg46-72pp was published on September 15, 2025 and was last updated on September 16, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

[email protected] contains malware after npm account takeoverGHSA-qrmh-qg46-72pp

GHSA-qrmh-qg46-72pp is a CWE-506 vulnerability in color. A fix is available for color — see the affected versions and patch details below.

Also known asCVE-2025-59143 GHSA-j8fv-6x8p-p766MAL-2025-46985

Published

Sep 15, 2025

Updated

Sep 16, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-qrmh-qg46-72pp.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦color

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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'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:

Bluesky, package owner: https://bsky.app/profile/bad-at-computer.bsky.social
debug repository, tracking issue (applies to all packages affected in the breach): https://github.com/debug-js/debug/issues/1005

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`color`	≥ 5.0.1&&< 5.0.2	5.0.2`npm install color@5.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for color, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update color to 5.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qrmh-qg46-72pp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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'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 ch

O3 Security · Impact-Aware SCA

Is GHSA-qrmh-qg46-72pp in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works