Critical Malicious Code Vulnerability in colour-name Package

colour-name Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17300: Malicious code in colour-name (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The colour-name package is an npm library that provides a collection of color names and their corresponding hex values. It is widely used in web development for styling and design purposes. However, this package has been found to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the colour-name package. This code can potentially compromise the integrity of applications, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions starting from 0, making it critical for developers to address it immediately.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall colour-name

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If an immediate update is not feasible, consider removing the colour-name package from your project until a safe version is available. You can do this by executing: npm uninstall colour-name.

Conclusion

The discovery of malicious code in the colour-name package highlights the importance of regularly monitoring and updating dependencies in software projects. Developers should take immediate action to mitigate risks by updating or removing the affected package.

See every vulnerability recorded for colour-name →

Share this vulnerability

FAQ

The colour-name package is an npm library that provides a list of color names and their hex values, commonly used in web development.

The specific details of the malicious code have not been disclosed, but it poses risks such as unauthorized access and data breaches.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Yes, updating to the latest version of the colour-name package will address the vulnerability. Use 'npm update colour-name' to ensure you have the patched version.

If you cannot update the package, consider uninstalling it temporarily until a safe version is available by running 'npm uninstall colour-name'.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall colour-name

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

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 →
Help improve this record
Report an issue or send feedback