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

Summary

02/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1118: Malicious code in @daffadeveloper/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 @daffadeveloper/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 and secure communication. However, this package has been compromised, embedding malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the @daffadeveloper/libsignal-node package. Any system with this package installed is considered fully compromised, as it may allow unauthorized access to sensitive information, including secrets and keys. The malicious code can lead to severe ramifications, including data breaches and loss of control over the affected system. The vulnerability is classified under CWE-506, indicating that the product contains code that appears to be malicious in nature.

How To Fix

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

npm uninstall @daffadeveloper/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 compromised package and secure your system.

Conclusion

The @daffadeveloper/libsignal-node package has been compromised with malicious code, posing serious security threats to any system using it. Immediate removal of the package and rotation of all sensitive information is essential to mitigate risks. Users are encouraged to monitor their systems for vulnerabilities using tools like Vulert.

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

Share this vulnerability

FAQ

Immediately remove the package and rotate all secrets and keys 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 installation.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

It is strongly advised not to use this package until a secure version is released, as it poses significant security risks.

How To Fix

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

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