Critical Malicious Code Vulnerability in @mailpoet/components Package

@mailpoet/components Updated 22 Jan 2026

Summary

22/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-455: Malicious code in @mailpoet/components (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

The @mailpoet/components package is a library used in Node.js applications, primarily for managing email functionalities within web applications. It provides various components that facilitate email creation, management, and delivery. However, this package has been found to contain malicious code, posing a significant risk to any system utilizing it.

Vulnerability Detail

The vulnerability originates from a malicious code embedded within the @mailpoet/components package. This code can compromise any computer that has the package installed, potentially granting unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it may lead to complete control of the affected system 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 @mailpoet/components

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.

Conclusion

The discovery of malicious code within the @mailpoet/components package poses a serious threat to users and systems utilizing it. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring of dependencies using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for @mailpoet/components →

Share this vulnerability

FAQ

You should immediately remove the package from your system and rotate any sensitive information stored on that computer.

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

Failure to address this vulnerability may result in unauthorized access to your system, leading to data breaches and potential loss of sensitive information.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Vulert monitors open-source vulnerabilities in your software by analyzing the package-lock.json file, providing real-time alerts without requiring code access.

How To Fix

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

npm uninstall @mailpoet/components

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