Critical Malicious Code Vulnerability in tor-libsignal Package

tor-libsignal Updated 21 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-398: Malicious code in tor-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

The tor-libsignal package is an npm library designed for secure messaging and communication. It leverages the Signal Protocol to provide end-to-end encryption for messages. However, this package has been compromised, leading to severe security risks for any application utilizing it. The malicious code embedded in this package can potentially allow unauthorized access to sensitive data and control over the affected systems.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the tor-libsignal package, identified as GHSA-4x99-4pvp-6hgp. This code can compromise any computer that has the package installed, leading to a complete takeover of the system. Users are advised to consider their systems fully compromised, as the malicious code may persist even after the package is removed. The implications of this vulnerability include unauthorized access to secrets and keys stored on the affected systems, posing a significant risk to user privacy and data integrity.

How To Fix

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

npm uninstall tor-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 to mitigate the risks posed by this vulnerability. The only recommended action is to remove the tor-libsignal package and rotate any sensitive information.

Conclusion

The tor-libsignal package has been compromised with malicious code, posing significant risks to any systems using it. Immediate action is required to remove the package and secure sensitive information. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for tor-libsignal →

Share this vulnerability

FAQ

You should immediately remove the tor-libsignal package and rotate any secrets or keys stored on your system.

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

Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential control over your system by malicious actors.

While removing the package is essential, you should also rotate all sensitive information and ensure that your system is secure from further threats.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json, allowing you to stay informed about potential risks.

How To Fix

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

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