Critical Malicious Code Vulnerability in colour-name Package
Summary
MAL-2025-17300: Malicious code in colour-name (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
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 →
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'.