Malicious Package in colour-string

colour-string Updated 02 Oct 2025

Summary

02/09/2020
CRITICAL
No i
Critical
9.8

GHSA-8mmf-qp7j-2w24: Malicious Package in colour-string. 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-string package is an npm package used for manipulating and converting color strings. It provides functions to parse, modify, and generate color strings in various formats. The package is widely used in JavaScript projects that involve color manipulation and rendering. However, version 1.5.3 of the colour-string package contained a malicious code as a preinstall script.

Vulnerability Detail

The malicious code in version 1.5.3 of colour-string package downloaded a file from a remote server, executed it, and opened a backdoor. This means that any computer with 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. Removing the package may not guarantee the removal of all malicious software resulting from its installation.

How To Fix

No fixed version is published for this vulnerability.

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

Workaround

There is no known workaround for this vulnerability. It is crucial to follow the recommended steps to fix the issue and mitigate any potential damage caused by the malicious code.

Conclusion

The colour-string package version 1.5.3 contained a malicious code that compromised the security of systems where it was installed. It is crucial to follow the recommended steps to fix the vulnerability, including rotating all secrets and keys stored on the affected systems. Conducting a thorough security audit and implementing additional security measures is also advised. For further support and assistance, you can contact DevNack.com.

See every vulnerability recorded for colour-string →

Share this vulnerability

FAQ

The impact of this vulnerability is severe as it allows an attacker to gain full control of the compromised system. All secrets and keys stored on the affected computer should be rotated immediately to prevent unauthorized access.

If you have version 1.5.3 of the colour-string package installed, your system is potentially affected. It is recommended to conduct a thorough security audit and follow the steps mentioned in the 'how_to_fix' section.

Removing the colour-string package is an essential step to mitigate the vulnerability. However, it is important to note that there is no guarantee that all malicious software resulting from its installation will be removed. Conducting a security audit and following the recommended steps is crucial.

Specific exploits or attacks leveraging this vulnerability have not been mentioned in the provided information. However, given the severity of the issue, it is important to assume that the compromised systems may have been accessed and manipulated by an outside entity.

If you need further assistance or support regarding this vulnerability and its remediation, you can reach out to info@devnack.com. They can provide expert guidance and help you secure your systems.

Related vulnerabilities

Recent vulnerabilities recorded for colour-string.

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

No fixed version is published for this vulnerability.

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