Critical Malicious Code Vulnerability in chai-as-awaited Package

chai-as-awaited Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192622: Malicious code in chai-as-awaited (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The chai-as-awaited package is a utility for integrating asynchronous assertions into the Chai assertion library, commonly used in JavaScript testing. It allows developers to write cleaner and more readable tests for asynchronous code. However, this package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the chai-as-awaited package. This code can fully compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive data such as secrets and keys. The origin of this malicious code is traced back to a known malware source, indicating that systems using this package are at high risk of being exploited by external entities.

How To Fix

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

npm uninstall chai-as-awaited

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, the best workaround is to uninstall the chai-as-awaited package entirely. You can do this by running the following command in your terminal: npm uninstall chai-as-awaited. Ensure that you also check for any other dependencies that may rely on this package.

Conclusion

The discovery of malicious code within the chai-as-awaited package poses a significant threat to users and their systems. Immediate action is required to mitigate risks, including uninstalling the package and securing sensitive information. Continuous monitoring for updates and patches is essential to ensure system safety.

See every vulnerability recorded for chai-as-awaited →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information 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 needing to sign up.

As of now, there is no patched version available. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation by malicious actors.

No, it is highly recommended to stop using chai-as-awaited until a secure version is released and the vulnerability is resolved.

How To Fix

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

npm uninstall chai-as-awaited

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