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

@sanzxcode/libsignal-node Updated 02 Mar 2026

Summary

02/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1122: Malicious code in @sanzxcode/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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The @sanzxcode/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 utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @sanzxcode/libsignal-node package. This code can fully compromise any computer that has the package installed or running, leading to potential data breaches and unauthorized access to sensitive information. Users are advised to treat any system with this package as fully compromised, necessitating immediate action to secure any secrets or keys stored on the affected machine.

How To Fix

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

npm uninstall @sanzxcode/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

Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability other than removing the package entirely.

Conclusion

The @sanzxcode/libsignal-node package has been compromised with malicious code, posing significant security risks. Immediate action is required to remove the package and secure any sensitive information. Utilize tools like Vulert to monitor for vulnerabilities in your applications.

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

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any secrets or keys stored on the affected computer.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete compromise of the affected system.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

It is advisable to review the security history and community feedback of other packages from the same author before using them.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall @sanzxcode/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