Malicious Code Vulnerability in chai-conf Package

chai-conf Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1678: Malicious code in chai-conf (npm). Affects chai-conf versions 1.1.7. 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 Your last release was probably never penetration tested 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-conf package is a configuration management tool for the Chai assertion library, commonly used in JavaScript testing. It allows developers to manage configurations easily and integrates seamlessly with various testing frameworks. However, this package has been identified to contain malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the chai-conf package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was identified in version 1.1.7 of the package, and it is crucial for developers to be aware of the potential ramifications of using this compromised version.

How To Fix

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

npm uninstall chai-conf

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 remove the chai-conf package from your project until a secure version is released. You can do this by running the following command: npm uninstall chai-conf. This will help mitigate the risk while you await a fix.

Conclusion

The discovery of malicious code in the chai-conf package highlights the importance of maintaining secure dependencies in software development. Developers should take immediate action to update or remove the affected package to protect their applications from potential threats.

See every vulnerability recorded for chai-conf →

Share this vulnerability

FAQ

Chai-conf is a configuration management tool for the Chai assertion library, used primarily in JavaScript testing.

The malicious code can lead to unauthorized access and potential data breaches in applications that use the compromised package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Yes, it is recommended to update the chai-conf package to a secure version as soon as it is available.

If you cannot update the package, consider removing it from your project as a temporary measure to mitigate risks.

How To Fix

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

npm uninstall chai-conf

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