Critical Malicious Code Vulnerability in https-servers Package

https-servers Updated 05 Feb 2026

Summary

05/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-769: Malicious code in https-servers (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

The https-servers package is a Node.js library designed to facilitate the creation of secure HTTP servers. It is commonly used in web applications to ensure encrypted communication between clients and servers. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the https-servers package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to complete control of the affected computer by an external entity. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall https-servers

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. The only recommended action is to remove the package entirely and secure your system.

Conclusion

The discovery of malicious code within the https-servers package poses a significant threat to users and their systems. 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 https-servers →

Share this vulnerability

FAQ

You should immediately remove the https-servers package and rotate all sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential control by malicious actors.

Currently, there is no patch available for the https-servers package. The best course of action is to remove it entirely.

If your application relies on the https-servers package for secure communication, you will need to find an alternative solution to maintain security.

How To Fix

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

npm uninstall https-servers

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