Critical Malicious Code Vulnerability in @protonme/routing Package

@protonme/routing Updated 24 Feb 2026

Summary

24/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1024: Malicious code in @protonme/routing (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 @protonme/routing package is a JavaScript library used in Node.js applications for routing functionalities. It is part of the npm ecosystem and is designed to facilitate the management of application routes. However, this package has been identified as containing malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @protonme/routing package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package being flagged as malicious by security researchers, indicating that it may have been intentionally tampered with to exploit users.

How To Fix

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

npm uninstall @protonme/routing

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. Users should ensure that they do not use any functionality provided by the @protonme/routing package until it is confirmed safe.

Conclusion

The @protonme/routing package has been identified as containing malicious code, posing severe risks to systems that utilize it. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for @protonme/routing →

Share this vulnerability

FAQ

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

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

No, there is currently no patched version available for this package. The only solution is to remove it.

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

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, providing an easy way to stay informed.

How To Fix

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

npm uninstall @protonme/routing

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