Critical Malicious Code Vulnerability in jest-node-paramset Package

jest-node-paramset Updated 26 Feb 2026

Summary

26/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1045: Malicious code in jest-node-paramset (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

jest-node-paramset is an npm package designed for parameter setting in Jest testing framework environments. It allows developers to manage test parameters effectively, enhancing the testing process. However, this package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the jest-node-paramset package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code falls under CWE-506, indicating that the product contains embedded malicious code. The ramifications of this vulnerability are significant, as it can lead to data breaches and unauthorized control over affected systems.

How To Fix

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

npm uninstall jest-node-paramset

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 workaround, if you must continue using the functionality provided by jest-node-paramset, consider isolating the environment in which it runs, such as using a virtual machine or container. This can help mitigate the risk of exposure to the host system.

Conclusion

The jest-node-paramset package has been identified as containing malicious code that poses a significant security threat. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for jest-node-paramset →

Share this vulnerability

FAQ

Immediately remove the package and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Currently, 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 sensitive data, potential data breaches, and complete control of the affected system by malicious actors.

It is highly discouraged to continue using jest-node-paramset due to its malicious nature. If you must use it, ensure you are operating in a secure and isolated environment.

How To Fix

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

npm uninstall jest-node-paramset

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