Critical Malicious Code Vulnerability in chai-min Package

chai-min Updated 08 Jan 2026

Summary

08/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-159: Malicious code in chai-min (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The chai-min package is a lightweight assertion library for Node.js and browsers, designed to facilitate testing by providing a simple syntax for writing assertions. It is commonly used in JavaScript testing frameworks. However, this package has been found to contain malicious code, posing significant security risks to any application that utilizes it.

Vulnerability Detail

The vulnerability originates from the discovery of embedded malicious code within the chai-min package. This code can compromise the integrity of any system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that systems using this package should be considered fully compromised, and there is no guarantee that simply removing the package will eliminate all traces of the malicious software.

How To Fix

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

npm uninstall chai-min

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 workaround, you can prevent the use of the chai-min package in your application by removing it from your dependencies and replacing it with a secure alternative assertion library, such as chai or another well-maintained package.

Conclusion

The discovery of malicious code in the chai-min package poses a serious threat to applications that utilize it. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring of dependencies is crucial to maintain the security of your applications.

See every vulnerability recorded for chai-min →

Share this vulnerability

FAQ

Immediately remove the chai-min package from your project and rotate any secrets or keys stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Currently, there is no patched version available for chai-min. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access to sensitive information and potential complete compromise of your system.

While many packages are safe, it is essential to regularly monitor and audit your dependencies for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall chai-min

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