VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

color: vulnerability history, versions and safety

color is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 51 releases, first recorded in Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 H1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all color vulnerabilities

Vulert verdict on color 5.0.3 i

Updated on 23 Oct 2026

Careful: 5.0.3 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

The current release contains malicious code, which caps this score.

What to do: Do not resolve 5.0.3 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 5.0.3 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 15 Sep 2025 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Depended on by 52,901 packages i
  • Stars 4,933 i
  • OpenSSF scorecard 2/10 i
  • Last release 11 months ago i
  • Licence MIT i
  • Similar names colors i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for color, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.0.3 14 Nov 2025 C1 malicious MIT No Details →
5.0.2 13 Sep 2025 C1 malicious MIT No Details →
5.0.0 12 Feb 2025 C1 malicious MIT No Details →
4.2.3 05 Apr 2022 C1 malicious MIT No Details →
4.2.2 05 Apr 2022 C1 malicious MIT No Details →
4.2.1 11 Feb 2022 C1 malicious MIT No Details →
4.2.0 11 Jan 2022 C1 malicious MIT No Details →
4.1.0 03 Dec 2021 C1 malicious MIT No Details →
4.0.2 26 Nov 2021 C1 malicious MIT No Details →
4.0.1 04 Aug 2021 C1 malicious MIT No Details →
3.2.1 18 Jul 2021 C1 malicious MIT No Details →
4.0.0 17 Jul 2021 C1 malicious MIT No Details →
3.2.0 17 Jul 2021 C1 malicious MIT No Details →
3.1.4 17 Jul 2021 C1 malicious MIT No Details →
3.1.3 09 Oct 2020 C1 malicious MIT No Details →
3.1.2 03 Jun 2019 C1 malicious MIT No Details →
3.1.1 23 Apr 2019 C1 malicious MIT No Details →
3.1.0 09 Oct 2018 C1 malicious MIT No Details →
3.0.0 25 Jan 2018 C1 malicious MIT No Details →
2.0.1 09 Nov 2017 C1 malicious MIT No Details →
2.0.0 29 Jun 2017 C1 malicious MIT No Details →
1.0.3 15 Dec 2016 C1 malicious MIT No Details →
1.0.2 06 Dec 2016 C1 malicious MIT No Details →
1.0.1 03 Dec 2016 C1 malicious MIT No Details →
1.0.0 03 Dec 2016 C1 malicious MIT No Details →
0.11.4 01 Nov 2016 C1 malicious MIT No Details →
0.11.3 24 Jun 2016 C1 malicious MIT No Details →
0.11.2 21 Jun 2016 C1 malicious MIT No Details →
0.11.1 03 Jan 2016 C1 malicious MIT No Details →
0.11.0 02 Jan 2016 C1 malicious MIT No Details →
0.10.1 02 Jul 2015 C1 malicious MIT No Details →
0.10.0 02 Jul 2015 C1 malicious MIT No Details →
0.9.0 21 Jun 2015 C1 malicious MIT No Details →
0.8.0 03 Mar 2015 C1 malicious MIT No Details →
0.7.3 17 Oct 2014 C1 malicious MIT No Details →
0.7.2 17 Oct 2014 C1 malicious MIT No Details →
0.7.1 23 Jul 2014 C1 malicious MIT No Details →
0.7.0 23 Jul 2014 C1 malicious MIT No Details →
0.6.0 27 Apr 2014 C1 malicious MIT No Details →
0.5.0 18 Nov 2013 C1 malicious MIT No Details →
0.4.4 07 Apr 2013 C1 malicious MIT No Details →
0.4.3 07 Apr 2013 C1 malicious MIT No Details →
0.4.2 14 Feb 2013 C1 malicious MIT No Details →
0.4.1 16 Oct 2011 C1 malicious MIT No Details →
0.4.0 31 Aug 2011 C1 malicious MIT No Details →
0.3.0 28 Jun 2011 C1 malicious MIT No Details →
0.2.0 27 Jun 2011 C1 malicious MIT No Details →
0.1.3 27 Jun 2011 C1 malicious MIT No Details →
0.1.2 24 Jun 2011 C1 malicious MIT No Details →
0.1.1 23 Jun 2011 C1 malicious MIT No Details →
0.1.0 23 Jun 2011 C1 malicious MIT No Details →

All 51 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for color

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-59143: color Package Malware Injection Due to npm Account Takeover 8.8 high 5.0.2 15 Sep 2025
Critical Malicious Code Vulnerability in Color Package (npm) N/A critical No fix published 08 Sep 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About color

Is color safe to use?

Vulert records 2 vulnerabilities for color in npm: 1 critical, 1 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is color's Vulert package health score?

Vulert scores color 15/100, which reads as critical. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release contains malicious code, which caps this score.

Is the latest version of color affected?

Yes. 5.0.3, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of color should I use?

5.0.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does color have?

2 vulnerabilities are recorded for color in the npm ecosystem: 1 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new color vulnerabilities disclosed?

0 vulnerabilities were recorded for color in the last 12 months, and the oldest entry in this database dates to 08 Sep 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of color are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor color for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the color version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.