Critical Malicious Code Vulnerability in @dinzid04/libsignal-node Package
Summary
MAL-2026-1392: Malicious code in @dinzid04/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 @dinzid04/libsignal-node package is a Node.js library designed for implementing the Signal Protocol, which provides end-to-end encryption for messaging applications. This package is utilized by developers to ensure secure communication in their applications. However, it has been compromised, leading to significant security risks for any system using it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @dinzid04/libsignal-node package. This code can fully compromise any computer that has the package installed or running, 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 in the package, which can lead to severe ramifications, including data breaches and loss of control over affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @dinzid04/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
There are no effective workarounds to mitigate the risks associated with this vulnerability. The best course of action is to remove the package entirely and ensure that all sensitive information is secured.
Conclusion
The @dinzid04/libsignal-node package has been compromised with malicious code, posing a significant security threat to any system using it. Immediate action is required to remove the package and secure sensitive information. Regular monitoring for vulnerabilities, such as using Vulert, can help prevent future incidents.
See every vulnerability recorded for @dinzid04/libsignal-node →
FAQ
You should remove the package immediately and rotate all sensitive information stored on the affected system.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your system.
While removing the package is essential, you should also rotate all secrets and keys from a secure computer to mitigate the risks of compromise.
If a patched version is released, updating the package may resolve the issue. However, it is crucial to remove the compromised package first.
