Critical Malicious Code Vulnerability in chai-sub Package

chai-sub Updated 28 Jan 2026

Summary

28/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-588: Malicious code in chai-sub (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 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-sub package is an npm library that extends the Chai assertion library, allowing for more expressive assertions in JavaScript testing. It is commonly used in conjunction with testing frameworks to enhance the readability and maintainability of test cases. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the chai-sub package, which has been identified as a serious threat. Any system running this package is considered fully compromised, potentially allowing attackers to access sensitive information such as secrets and keys. The malicious code can execute arbitrary commands, leading to further exploitation of the affected system. Users are advised to treat any computer with this package installed as compromised and take immediate action.

How To Fix

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

npm uninstall chai-sub

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

Currently, there are no effective workarounds to mitigate the risks associated with the chai-sub package. The only recommended action is to uninstall the package and secure your environment.

Conclusion

The discovery of malicious code in the chai-sub package poses a significant threat to users. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for chai-sub →

Share this vulnerability

FAQ

Immediately uninstall the chai-sub package and rotate any sensitive information stored on the affected machine.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

No, there is currently no patched version available for the chai-sub package. The only solution is to uninstall it.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall chai-sub

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