Critical Malicious Code Vulnerability in @shenira/libsignal-node Package

@shenira/libsignal-node Updated 06 Mar 2026

Summary

06/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1268: Malicious code in @shenira/libsignal-node (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @shenira/libsignal-node package is a Node.js library designed for implementing the Signal Protocol, which is used for secure messaging. It provides functionalities for end-to-end encryption and is commonly utilized in applications that prioritize user privacy and data security. However, this package has been identified as containing malicious code, which poses significant risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @shenira/libsignal-node package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has inserted harmful code into the package, making any computer running this package fully compromised. Users are advised to treat any system with this package installed as potentially under the control of an external entity.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @shenira/libsignal-node

If 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. The only recommended action is to remove the package entirely and secure your system.

Conclusion

The @shenira/libsignal-node package has been compromised with malicious code, posing severe risks to any system where it is installed. Immediate removal of the package and rotation of sensitive information is crucial to mitigate potential damage. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for @shenira/libsignal-node →

Share this vulnerability

FAQ

You should remove the package immediately and rotate all sensitive information 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 requiring any signup.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete control of your system by malicious actors.

While removing the package is essential, there is no guarantee that all malicious software will be removed. It is advisable to perform a thorough security audit and restore from backups if necessary.

It is advisable to exercise caution and review other packages from the same author, as they may also pose similar risks. Always verify the integrity of packages before installation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @shenira/libsignal-node

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback