Critical Malicious Code Vulnerability in @dgxeon/libsignal-node Package
Summary
MAL-2026-1072: Malicious code in @dgxeon/libsignal-node (npm). Affected versions are not published. 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 @dgxeon/libsignal-node package is a Node.js library designed for implementing the Signal Protocol, which is used for secure messaging. This package is intended for developers looking to integrate end-to-end encryption into their applications. However, it has been found to contain malicious code that compromises the security of any system where it is installed.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @dgxeon/libsignal-node package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package being flagged as malware by security researchers, indicating that it contains embedded malicious code that poses significant risks to users and their data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @dgxeon/libsignal-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, ensure that you do not use the @dgxeon/libsignal-node package in your projects. Instead, consider using alternative libraries that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The @dgxeon/libsignal-node package has been identified as containing malicious code that poses a significant security risk. Users are advised to uninstall the package immediately and take necessary precautions to secure their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for @dgxeon/libsignal-node →
FAQ
Immediately uninstall the package and rotate any secrets or keys stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
No, there is currently no patched version of the package available. It is recommended to remove it entirely.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potentially compromising user privacy and security.
Yes, you can report vulnerabilities to the package maintainers or relevant security organizations to help improve the ecosystem.
