Critical Malicious Code Vulnerability in dzyclutch-libsignal-node Package

dzyclutch-libsignal-node Updated 05 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17621: Malicious code in dzyclutch-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 dzyclutch-libsignal-node package is an npm library designed for handling signal protocol operations. It is utilized in applications requiring secure messaging and communication. However, this package has been compromised, embedding malicious code that poses significant security risks to any system using it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the dzyclutch-libsignal-node package. Any system with this package installed is considered fully compromised, allowing unauthorized access to sensitive information such as secrets and keys. The malicious code can lead to severe ramifications, including data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall dzyclutch-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 for this vulnerability other than removing the package and securing the environment. It is essential to monitor your systems for any signs of compromise.

Conclusion

The dzyclutch-libsignal-node package has been compromised with malicious code, posing a significant threat to any system using it. Immediate action is required to remove the package and secure sensitive information. Utilize tools like Vulert to monitor for vulnerabilities in your applications.

See every vulnerability recorded for dzyclutch-libsignal-node →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information that may have been compromised.

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

No, there is currently no patched version available for this package.

Failing to remove the package could lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring your software remains secure.

How To Fix

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

npm uninstall dzyclutch-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