Critical Malicious Code Vulnerability in eslint-supertest Package

eslint-supertest Updated 06 Jan 2026

Summary

06/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-58: Malicious code in eslint-supertest (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

eslint-supertest is an npm package that integrates ESLint with Supertest, allowing developers to run HTTP assertions on their Node.js applications. It is commonly used in testing environments to ensure that APIs behave as expected. However, this package has been compromised, leading to severe security risks for any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the eslint-supertest package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has manipulated the package, making it imperative for users to take immediate action to secure their systems.

How To Fix

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

npm uninstall eslint-supertest

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

There are no effective workarounds for this vulnerability other than removing the package and ensuring that all sensitive information is secured. Users should avoid using eslint-supertest until a verified and safe version is available.

Conclusion

The eslint-supertest package has been compromised with malicious code, posing a significant risk to any systems that have it installed. Immediate removal of the package and rotation of sensitive information is essential. Users should stay vigilant and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for eslint-supertest →

Share this vulnerability

FAQ

You should immediately remove the eslint-supertest package and rotate any sensitive information stored on your system.

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

Currently, there is no patched version available. Users are advised to remove the package entirely.

Failure to address this vulnerability could lead to unauthorized access to sensitive data and full compromise of your system.

Vulert monitors and alerts users in real-time for open-source vulnerabilities using just the package-lock.json file, providing an easy way to stay informed.

How To Fix

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

npm uninstall eslint-supertest

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