Malicious Code Vulnerability in path-to-regexp-updated Package
Summary
MAL-2026-1808: Malicious code in path-to-regexp-updated (npm). Affects path-to-regexp-updated versions 99.99.1 – 99.99.2. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The path-to-regexp-updated package is a popular npm library used for matching and parsing URL paths. It allows developers to define route patterns and extract parameters from URLs, making it essential for web applications that rely on routing. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.
Vulnerability Detail
The vulnerability stems from malicious code embedded within specific versions of the path-to-regexp-updated package (versions 99.99.1 and 99.99.2). This code can lead to unauthorized access, data breaches, or other malicious activities within an application. The origin of this vulnerability is linked to the package being compromised, which can have severe ramifications for any application relying on it for routing functionalities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall path-to-regexp-updatedIf 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 temporary workaround, you can remove the path-to-regexp-updated package from your project and replace it with an alternative routing library that does not have known vulnerabilities. This can be done by uninstalling the package with the command: npm uninstall path-to-regexp-updated.
Conclusion
The path-to-regexp-updated package has been identified with a serious vulnerability due to malicious code in specific versions. It is crucial for developers to update to a secure version or find alternatives to ensure the safety and integrity of their applications. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities.
See every vulnerability recorded for path-to-regexp-updated →
FAQ
Versions 99.99.1 and 99.99.2 of the path-to-regexp-updated package are known to contain malicious code.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner without needing to sign up.
Using the compromised package can lead to unauthorized access, data breaches, and other malicious activities that can compromise the security of your application.
Regularly updating your dependencies, using tools like Vulert for monitoring vulnerabilities, and conducting security audits can help prevent such issues.
If you cannot update the package immediately, consider removing it and using an alternative library until a secure version is available.
