Critical Malicious Code Vulnerability in @emilgroup/gdv-sdk-node Package
Summary
MAL-2026-2049: Malicious code in @emilgroup/gdv-sdk-node (npm). Affects @emilgroup/gdv-sdk-node versions >= 2.6.1, <= 2.6.3. 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/gdv-sdk-node package is a Node.js SDK designed for integrating with the Emil Group's services. It provides developers with tools to interact with various APIs, facilitating seamless data exchange and functionality. However, this package has been identified as containing malicious code, posing significant security risks to any system utilizing it.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within versions 2.6.1 to 2.6.3 of the @emilgroup/gdv-sdk-node package. Any system running this package is considered fully compromised, with potential unauthorized access to sensitive information such as secrets and keys. The malicious code may allow external entities to gain control over 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/gdv-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, if immediate upgrading is not feasible, consider isolating the affected system from the network to prevent further exploitation. However, this is only a temporary measure, and the package should be removed as soon as possible.
Conclusion
The @emilgroup/gdv-sdk-node package has been compromised with malicious code, affecting versions 2.6.1 to 2.6.3. It is imperative to update to a secure version and take immediate action to protect sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for @emilgroup/gdv-sdk-node →
FAQ
Immediately remove the package and rotate any secrets or keys stored on the affected system.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Yes, updating to a version later than 2.6.3 will resolve the issue, as those versions do not contain the malicious code.
Failure to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.
Yes, but ensure you install a safe, updated version of the package to avoid future vulnerabilities.
