Critical Malicious Code Vulnerability in @emilgroup/payment-sdk
Summary
MAL-2026-2056: Malicious code in @emilgroup/payment-sdk (npm). Affects @emilgroup/payment-sdk versions >= 1.15.1, <= 1.15.2. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The @emilgroup/payment-sdk is a JavaScript library available on npm that facilitates payment processing functionalities for applications. It is designed to integrate payment solutions seamlessly into web applications, providing developers with tools to manage transactions securely. However, recent findings have revealed that versions 1.15.1 to 1.15.2 of this package contain malicious code, posing significant security risks to users and their systems.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the @emilgroup/payment-sdk package, specifically in versions 1.15.1 and 1.15.2. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this malicious code is linked to a security breach, and it is classified under CWE-506, indicating that the product contains code that appears to be malicious in nature. Users are advised to consider their systems fully compromised if they have this package installed.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @emilgroup/payment-sdkIf 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 temporary workaround, users should remove the affected package from their projects. This can be achieved by running the command: npm uninstall @emilgroup/payment-sdk. However, be aware that simply removing the package may not eliminate all malicious software that may have been installed as a result of the compromise.
Conclusion
The discovery of malicious code in the @emilgroup/payment-sdk package poses a serious threat to users and their systems. Immediate action is required to remove the affected versions and update to a secure release. Users should also rotate any sensitive information that may have been compromised. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.
See every vulnerability recorded for @emilgroup/payment-sdk →
FAQ
You should immediately uninstall the affected package and update to the latest version to mitigate the risks.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.
Yes, Vulert provides a service that monitors your package-lock.json file for open-source vulnerabilities in real-time.
CWE-506 indicates that the product contains code that appears to be malicious in nature, highlighting the security risks associated with the affected package.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
