Critical Malicious Code Vulnerability in @emilgroup/document-sdk-node Package
Summary
MAL-2026-2075: Malicious code in @emilgroup/document-sdk-node (npm). Affects @emilgroup/document-sdk-node versions >= 1.43.1, <= 1.43.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/document-sdk-node package is a Node.js library designed for document management and processing. It provides developers with tools to integrate document functionalities into their applications. However, this package has been identified to contain malicious code, posing significant security risks to any system utilizing it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within versions 1.43.1 to 1.43.2 of the @emilgroup/document-sdk-node package. Any system running this package is considered fully compromised, with potential exposure of sensitive information such as secrets and keys. The malicious code may allow unauthorized access and control over the affected systems, leading to severe security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @emilgroup/document-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
Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability other than removing the package entirely.
Conclusion
The @emilgroup/document-sdk-node package has been compromised with malicious code, posing a serious threat to any systems utilizing it. Immediate action is required to uninstall the package and secure any sensitive information. Utilize tools like Vulert to monitor for vulnerabilities in your applications.
See every vulnerability recorded for @emilgroup/document-sdk-node →
FAQ
You should immediately uninstall the @emilgroup/document-sdk-node package and rotate any sensitive information stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
No, there is currently no patched version available for the @emilgroup/document-sdk-node package. The only solution is to remove the package.
Failing to address this vulnerability may result in unauthorized access to your system, data breaches, and potential loss of sensitive information.
Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights without requiring access to the code.
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.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.