Critical Malicious Code Vulnerability in @mailpoet/component Package
Summary
MAL-2026-454: Malicious code in @mailpoet/component (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @mailpoet/component package is a widely used npm library that facilitates various functionalities for MailPoet, a popular email marketing service. This package is integral for developers looking to integrate email functionalities into their applications. However, it has recently been identified as containing malicious code, which poses a significant security risk to any system utilizing it.
Vulnerability Detail
The vulnerability originates from the presence of malicious code within the @mailpoet/component package. This code can compromise any computer that has the package installed or running, potentially allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it could lead to complete control of the affected system by an external entity. Users are advised to treat any system with 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/componentIf 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, there are no effective workarounds other than removing the package from your system. It is essential to monitor your systems for any signs of compromise and take necessary actions to secure your environment.
Conclusion
The discovery of malicious code in the @mailpoet/component package presents a serious security threat to users. Immediate action is required to remove the package and secure affected systems. Regular monitoring and vulnerability management are essential to protect against such risks in the future.
See every vulnerability recorded for @mailpoet/component →
FAQ
Immediately remove the package from your system and rotate any sensitive information stored on that machine.
Look for unusual activity, unauthorized access attempts, or any changes to your system that you did not initiate.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Failing to address this vulnerability could lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
