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

@xayz/libsignal-node Updated 08 Oct 2026

Summary

08/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17672: Malicious code in @xayz/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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @xayz/libsignal-node package is an npm library designed for implementing the Signal Protocol, which is used for secure messaging. It provides functionalities for end-to-end encryption, ensuring that messages are only readable by the intended recipients. However, this package has been identified as containing malicious code, posing significant security risks to any application that utilizes it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @xayz/libsignal-node package. Any system running this package is considered fully compromised, as it may allow unauthorized access to sensitive information, including secrets and keys stored on the affected computer. The malicious code can lead to severe ramifications, including data breaches and loss of control over the system. Users are advised to treat any installation of this package with extreme caution.

How To Fix

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

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

As there is no direct workaround to mitigate the effects of the malicious code, the only recommended action is to uninstall the package and secure the system. Regularly monitor your systems for any unusual activity and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The @xayz/libsignal-node package has been identified as containing malicious code, posing serious security risks. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies is essential to prevent future vulnerabilities.

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

Share this vulnerability

FAQ

It is an npm library for implementing the Signal Protocol, used for secure messaging and end-to-end encryption.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

You should uninstall the package immediately and rotate any secrets or keys stored on the affected system.

No, there is currently no patched version of the @xayz/libsignal-node package available.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application using the Vulert playground without any signup.

How To Fix

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

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