Malicious Package in path-to-regxep

path-to-regxep Updated 02 Oct 2025

Summary

03/09/2020
CRITICAL
No i
Critical
9.1

GHSA-f7gc-6hcj-wc42: Malicious Package in path-to-regxep. Affects path-to-regxep versions >= 0.0.0. 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 path-to-regxep package is an npm package used for regular expression matching and manipulation. It provides functions and utilities to work with regular expressions in JavaScript applications. The package is widely used in various projects and provides a convenient way to handle regular expressions. However, all versions of this package were found to contain malware that is designed to find and exfiltrate cryptocurrency wallets.

Vulnerability Detail

The vulnerability in the path-to-regxep package is due to the inclusion of malicious code in all versions of the package. This code is specifically designed to search for and steal cryptocurrency wallets. If a computer has this package installed or running, it should be considered fully compromised. Any secrets or keys stored on that computer should be rotated immediately from a different computer. Simply removing the package may not be sufficient, as the malicious software may have given outside entities full control of the computer.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to follow the recommended steps to fix the issue and ensure the security of the affected systems.

Conclusion

The path-to-regxep package has been found to contain a malicious package that can compromise the security of systems it is installed on. It is important to take immediate action to identify and mitigate the impact of this vulnerability. Follow the recommended steps to fix the issue, rotate keys and secrets, remove the package, and conduct a thorough security audit. For further support and assistance in vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for path-to-regxep →

Share this vulnerability

FAQ

The path-to-regxep package is an npm package used for regular expression matching and manipulation in JavaScript applications.

If a computer has the path-to-regxep package installed, it should be considered fully compromised. The malicious code in the package is designed to find and exfiltrate cryptocurrency wallets.

To fix this vulnerability, you should identify all computers with the package installed, rotate all secrets and keys stored on those computers, remove the package, and conduct a thorough security audit.

No, there is no known workaround for this vulnerability. It is essential to follow the recommended steps to fix the issue.

To ensure the security of your systems, it is crucial to regularly update and patch all software, conduct security audits, and follow best practices for secure coding and deployment.

How To Fix

No fixed version is published for this vulnerability.

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