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

@omhc/libsignal-node Updated 16 Mar 2026

Summary

16/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1439: Malicious code in @omhc/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 @omhc/libsignal-node package is a library designed for implementing the Signal Protocol in Node.js applications. It provides functionalities for secure messaging and is widely used in applications that require end-to-end encryption. However, this package has been compromised, leading to severe security risks for any application utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @omhc/libsignal-node 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 malicious nature of the code has been confirmed by security researchers, and it poses a significant threat to the integrity and confidentiality of affected systems.

How To Fix

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

npm uninstall @omhc/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 a workaround, you can temporarily switch to a different library that implements the Signal Protocol securely. Ensure that any sensitive data is handled with care and consider rotating all secrets and keys stored on the affected system.

Conclusion

The @omhc/libsignal-node package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for vulnerabilities in your software.

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

Share this vulnerability

FAQ

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

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

No, there is currently no patched version available for this package. It is recommended to remove it entirely.

Failing to address this vulnerability can lead to unauthorized access to sensitive information, potential data breaches, and complete compromise of your system.

Yes, you can use alternative libraries that implement the Signal Protocol securely. Research and select a reputable library to ensure the safety of your application.

How To Fix

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

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