Critical Malicious Code Vulnerability in @emilgroup/account-sdk-node Package
Summary
MAL-2026-2032: Malicious code in @emilgroup/account-sdk-node (npm). Affects @emilgroup/account-sdk-node versions >= 1.40.1, <= 1.40.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
Background
The @emilgroup/account-sdk-node package is a Node.js SDK designed for account management functionalities. It is utilized in various applications to facilitate user account operations. However, this package has been identified as containing malicious code, posing a significant security risk to any system where it is installed.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within versions 1.40.1 to 1.40.2 of the @emilgroup/account-sdk-node package. Any system running this package is considered fully compromised, allowing unauthorized access to sensitive information such as secrets and keys. The malicious code can lead to severe ramifications, including data breaches and loss of control over the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @emilgroup/account-sdk-nodeIf 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, it is recommended to uninstall the package using the command: npm uninstall @emilgroup/account-sdk-node. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.
Conclusion
The @emilgroup/account-sdk-node package has been compromised with malicious code, posing a serious threat to any system using it. Immediate action is required to mitigate risks, including uninstalling the package and securing sensitive information. Regular monitoring for vulnerabilities, such as through Vulert, is recommended to maintain application security.
See every vulnerability recorded for @emilgroup/account-sdk-node →
FAQ
Immediately uninstall the package and rotate any sensitive information that may have been compromised.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Currently, there is no patched version available. The best course of action is to uninstall the affected package.
Failure to address this vulnerability can lead to unauthorized access to sensitive data and potential control over your system by malicious actors.
It is highly discouraged to use the package in any capacity due to the inherent risks associated with the malicious code.
