Critical Malicious Code Vulnerability in https-emailjs Package

https-emailjs Updated 06 Feb 2026

Summary

04/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-724: Malicious code in https-emailjs (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-emailjs package is a Node.js library designed for sending emails using various email services. It simplifies the process of integrating email functionalities into applications. However, it has been found to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the https-emailjs 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 is classified under CWE-506, indicating that it embeds harmful functionalities within the software.

How To Fix

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

npm uninstall https-emailjs

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, you can temporarily switch to an alternative email library that does not have known vulnerabilities until the https-emailjs package is confirmed safe or patched. Consider using libraries such as nodemailer or emailjs.

Conclusion

The discovery of malicious code in the https-emailjs package poses a significant risk to users. Immediate action is required to remove the package and secure any compromised information. Staying informed about vulnerabilities and using monitoring tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for https-emailjs →

Share this vulnerability

FAQ

Immediately remove the package from your system 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.

Keeping the package can lead to unauthorized access to your system, potentially allowing attackers to steal sensitive information or take control of your computer.

The best mitigation is to remove the package entirely and use a different email library until a safe version is released.

Utilize tools like Vulert to monitor your dependencies for vulnerabilities in real-time.

How To Fix

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

npm uninstall https-emailjs

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.