Critical Malicious Code Vulnerability in dappa-libsignal Package

dappa-libsignal Updated 13 Mar 2026

Summary

12/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1358: Malicious code in dappa-libsignal (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

dappa-libsignal is an npm package that is designed to facilitate communication using the Signal protocol. It is intended for developers looking to implement secure messaging features in their applications. However, this package has been compromised, embedding malicious code that poses significant security risks to any system that installs it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the dappa-libsignal package. This code can fully compromise any computer that has the package installed, 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, which can lead to severe ramifications, including data breaches and loss of control over the affected system.

How To Fix

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

npm uninstall dappa-libsignal

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 other than removing the package entirely. It is recommended to monitor your system for any unusual activity after the package has been uninstalled.

Conclusion

The dappa-libsignal package has been identified as containing malicious code that can compromise systems. Immediate action is required to uninstall the package and secure any sensitive information. Utilize tools like Vulert to monitor for vulnerabilities in your applications.

See every vulnerability recorded for dappa-libsignal →

Share this vulnerability

FAQ

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

No, there is currently no patched version available for the dappa-libsignal package.

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

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall dappa-libsignal

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