Critical Malicious Code Vulnerability in @emilgroup/gdv-sdk Package
Summary
MAL-2026-2048: Malicious code in @emilgroup/gdv-sdk (npm). Affects @emilgroup/gdv-sdk versions >= 2.6.1, <= 2.6.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/gdv-sdk is an npm package designed to facilitate interactions with the GDV (General Data Verification) services. It provides developers with tools to integrate GDV functionalities into their applications seamlessly. However, this package has been compromised, leading to serious security concerns for users who have it installed.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @emilgroup/gdv-sdk package, specifically between versions 2.6.1 and 2.6.2. This malicious code can fully compromise any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who embedded harmful code into the package, posing a significant risk to users and their systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @emilgroup/gdv-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
There are no effective workarounds for this vulnerability other than removing the package and ensuring that your system is secure. It is recommended to monitor your system for any signs of compromise.
Conclusion
The @emilgroup/gdv-sdk package has been identified as containing malicious code, posing a severe risk to users. Immediate action is required to uninstall the package and secure any exposed secrets. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for @emilgroup/gdv-sdk →
FAQ
Immediately uninstall the package using 'npm uninstall @emilgroup/gdv-sdk' and rotate any sensitive keys or secrets.
You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Failing to address this vulnerability could lead to unauthorized access to sensitive data, potentially compromising your entire system.
No patch is available for the compromised versions. The best course of action is to uninstall the package.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated.
