Malicious Code Detected in jest-stable Package - Version 40.1.9

jest-stable Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192678: Malicious code in jest-stable (npm). Affects jest-stable versions 40.1.9. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The 'jest-stable' package is a variant of the popular Jest testing framework used in JavaScript applications. It is designed to facilitate unit testing and ensure code quality through automated testing. However, the specific version 40.1.9 has been flagged for malicious behavior, which undermines its reliability and poses security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the 'jest-stable' package arises from its ability to communicate with a domain linked to malicious activities and execute commands that are harmful. This behavior can lead to unauthorized access, data breaches, or the execution of arbitrary code within the user's environment, potentially compromising the integrity of the application and its data.

How To Fix

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

npm uninstall jest-stable

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, consider removing the 'jest-stable' package from your project until a secure version is released. You can do this by running the command: 'npm uninstall jest-stable'. Alternatively, you can use the original Jest package if it meets your testing requirements.

Conclusion

The 'jest-stable' package version 40.1.9 has been identified as malicious, posing significant security risks to applications that utilize it. It is crucial to update to a secure version or remove the package until a fix is available. Monitoring tools like Vulert can assist in identifying vulnerabilities in your software.

See every vulnerability recorded for jest-stable →

Share this vulnerability

FAQ

The 'jest-stable' package is a testing framework for JavaScript applications, designed to help developers write and run unit tests.

The malicious behavior was identified by the OpenSSF Package Analysis project, which flagged the package for communicating with a malicious domain and executing harmful commands.

Using the compromised version can lead to unauthorized access, data breaches, and execution of harmful commands, potentially compromising application security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check for vulnerabilities in your application without requiring access to the code or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall jest-stable

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