Malicious Code Detected in expectant Package - Security Alert

expectant Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20058: Malicious code in expectant (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 expectant package is a library in the npm ecosystem designed to facilitate asynchronous testing in JavaScript applications. It provides utilities for managing expectations in tests, making it easier for developers to write and maintain test cases. However, this package has been identified as containing malicious code, which poses a significant security risk to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the expectant package. This code can potentially compromise the integrity of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 of the package and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall expectant

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, if you cannot update the package immediately, consider removing the expectant package from your project and replacing it with an alternative testing library that does not have known vulnerabilities.

Conclusion

The expectant package has been identified as containing malicious code, posing a serious security risk to applications that utilize it. Users are urged to update the package to a secure version or consider alternative solutions to mitigate potential threats. Regular monitoring of dependencies is essential to maintain application security.

See every vulnerability recorded for expectant →

Share this vulnerability

FAQ

The expectant package is an npm library used for asynchronous testing in JavaScript applications.

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software without needing to access the code. Visit Vulert Scanner to check if your application is affected.

Consider removing the expectant package and replacing it with a secure alternative until you can update.

Utilize tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time, ensuring you are alerted to any issues promptly.

How To Fix

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

npm uninstall expectant

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