Critical Malicious Code Vulnerability in router-parse Package

router-parse Updated 02 Oct 2025

Summary

16/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5988: Malicious code in router-parse (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 router-parse package is an npm library used for parsing routing information in web applications. It is designed to facilitate the handling of URL routing, making it easier for developers to manage navigation within their applications. However, this package has been identified to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the router-parse package. This code can lead to a complete compromise of any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can result in data breaches and loss of control over affected systems. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall router-parse

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 associated with this vulnerability. The best course of action is to remove the package entirely and ensure that all sensitive information is secured.

Conclusion

The router-parse package contains a critical vulnerability due to embedded malicious code that can compromise any system where it is installed. Immediate removal of the package and rotation of sensitive information is necessary to mitigate risks. Users should remain vigilant and utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for router-parse →

Share this vulnerability

FAQ

router-parse is an npm package used for parsing routing information in web applications.

The malicious code can lead to unauthorized access to sensitive information and complete control of the affected system.

You should immediately remove the router-parse package and rotate any secrets or keys stored on the affected system.

Currently, there is no patched version available. The best action is to remove the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall router-parse

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