Critical Malicious Code Vulnerability in @emilgroup/payment-sdk-node Package

@emilgroup/payment-sdk-node Updated 22 Mar 2026

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2057: Malicious code in @emilgroup/payment-sdk-node (npm). Affects @emilgroup/payment-sdk-node versions >= 1.23.1, <= 1.23.2. 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 @emilgroup/payment-sdk-node package is a Node.js library designed for handling payment processing in applications. It provides developers with tools to integrate payment functionalities seamlessly. However, this package has been identified as containing malicious code, posing significant security risks to systems that utilize it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within versions 1.23.1 to 1.23.2 of the @emilgroup/payment-sdk-node package. Any system running this package is considered fully compromised, with potential unauthorized access to sensitive data, including secrets and keys. The malicious code can allow external entities to control the affected systems, leading to severe data breaches and loss of integrity.

How To Fix

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

npm uninstall @emilgroup/payment-sdk-node

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

Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability other than removing the package and securing your system.

Conclusion

The @emilgroup/payment-sdk-node package has been compromised with malicious code, posing serious security threats to any system using it. Immediate action is required to remove the package and secure any sensitive data. Regular monitoring of dependencies is essential to prevent future vulnerabilities.

See every vulnerability recorded for @emilgroup/payment-sdk-node →

Share this vulnerability

FAQ

Immediately uninstall the @emilgroup/payment-sdk-node package and rotate any sensitive keys or secrets stored on the compromised system.

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

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

There is no patch available for the affected versions. The only solution is to uninstall the package.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

How To Fix

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

npm uninstall @emilgroup/payment-sdk-node

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