Critical Malicious Code Vulnerability in @modss/libsignal Package

@modss/libsignal Updated 12 Oct 2026

Summary

12/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17823: Malicious code in @modss/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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @modss/libsignal package is a library designed for secure messaging and communication. It is utilized in various applications to facilitate encrypted messaging, ensuring user privacy and data security. However, this package has been compromised, leading to significant security risks for any system utilizing it. The malicious code embedded within this package can potentially grant unauthorized access to sensitive information stored on affected systems.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the @modss/libsignal package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control over the system. The ramifications include unauthorized access to secrets and keys, which can lead to further exploitation of the system and its data. The technical aspect of this 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 @modss/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

Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package and securing the system.

Conclusion

The @modss/libsignal package has been compromised with malicious code, posing a significant security risk to any system using it. Immediate action is required to uninstall the package and secure sensitive information. Regular monitoring of dependencies is essential to prevent future vulnerabilities.

See every vulnerability recorded for @modss/libsignal →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on your system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, potentially compromising user privacy and security.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure that you only use trusted packages.

CWE-506 indicates that the product contains embedded malicious code, highlighting the severity of the security risk posed by this vulnerability.

How To Fix

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

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