Malicious Code Detected in eslint-config-colourbox-example Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19824: Malicious code in eslint-config-colourbox-example (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The eslint-config-colourbox-example package is a configuration package for ESLint, a popular JavaScript linting utility. It is designed to help developers maintain code quality by enforcing coding standards and identifying potential errors in their JavaScript code. However, this package has been found to contain malicious code, posing a significant risk to users who incorporate it into their projects.

Vulnerability Detail

The vulnerability in the eslint-config-colourbox-example package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected applications. The malicious code was introduced in version 0 and has been identified as a serious threat to developers relying on this package for their projects.

How To Fix

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

npm uninstall eslint-config-colourbox-example

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

As a temporary measure, you can avoid using the eslint-config-colourbox-example package until a secure version is released. Consider using alternative ESLint configuration packages that do not have known vulnerabilities.

Conclusion

The eslint-config-colourbox-example package has been identified as containing malicious code, posing a serious threat to developers. It is crucial to remove this package from your projects and monitor for any updates or alternative packages to ensure the security of your applications.

See every vulnerability recorded for eslint-config-colourbox-example →

Share this vulnerability

FAQ

It is a configuration package for ESLint that helps enforce coding standards in JavaScript projects.

The package contains malicious code that can compromise application security.

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

Remove the package immediately and check for any updates or patches that may address the vulnerability.

Yes, consider using other ESLint configuration packages that are well-maintained and do not have known vulnerabilities.

How To Fix

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

npm uninstall eslint-config-colourbox-example

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