Critical Malicious Code Vulnerability in nextjs-https-supertest Package

nextjs-https-supertest Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5938: Malicious code in nextjs-https-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 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 nextjs-https-supertest package is an npm library designed to facilitate testing of HTTP requests in Next.js applications. It provides developers with tools to perform end-to-end testing by simulating server responses and handling HTTPS requests. However, this package has been identified to contain embedded malicious code, posing significant security risks to any application utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the nextjs-https-supertest package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that even after removal of the package, there is no guarantee that all traces of the malicious software will be eliminated. This vulnerability is classified under CWE-506, indicating that the code appears to be malicious in nature.

How To Fix

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

npm uninstall nextjs-https-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

Currently, the best workaround is to avoid using the nextjs-https-supertest package altogether until a secure version is released. If you need similar functionality, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The nextjs-https-supertest package contains embedded malicious code that poses a severe security risk to any system using it. Immediate action is required to uninstall the package and secure any compromised information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for nextjs-https-supertest →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information that may have been compromised.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Using such a package can lead to unauthorized access to sensitive data, potential data breaches, and complete compromise of the affected system.

While removing the package is necessary, there is no guarantee that all malicious software will be removed. It is essential to rotate any secrets and keys stored on the affected system.

Yes, consider using other testing libraries that do not have known vulnerabilities, such as supertest or axios for HTTP requests.

How To Fix

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

npm uninstall nextjs-https-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