Critical Malicious Code Vulnerability in @kinggupong/libsignal-node Package
Summary
MAL-2026-1367: Malicious code in @kinggupong/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 @kinggupong/libsignal-node package is a library designed for implementing the Signal Protocol in Node.js applications. It provides functionalities for secure messaging and encryption. However, this package has been compromised, leading to severe security risks for any application that utilizes it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @kinggupong/libsignal-node package. This code can fully compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code. Users should be aware that simply removing the package may not eliminate all traces of the malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @kinggupong/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, it is recommended to uninstall the package using the command: npm uninstall @kinggupong/libsignal-node. Additionally, monitor your system for any unusual activity and consider using alternative libraries that provide similar functionalities without the associated risks.
Conclusion
The @kinggupong/libsignal-node package has been identified as containing malicious code that poses significant security risks. It is essential to remove the package immediately and take necessary precautions to secure sensitive information. Users are encouraged to monitor their systems and consider alternative libraries for secure messaging functionalities.
See every vulnerability recorded for @kinggupong/libsignal-node →
FAQ
Immediately uninstall the 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 without needing to sign up.
After removing the package, ensure that all secrets and keys are rotated from a secure computer to mitigate any potential damage.
Leaving the package installed can lead to unauthorized access to sensitive data and full control of your computer by malicious actors.
Yes, consider using other libraries that implement the Signal Protocol without the associated risks of malicious code.
