Malicious Code Detected in glob-match Package - Security Advisory

glob-match Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21577: Malicious code in glob-match (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 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 glob-match package is a utility in the npm ecosystem that provides functionality for matching file paths against glob patterns. It is commonly used in various JavaScript applications for file handling and manipulation. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the glob-match package originates from the inclusion of malicious code that can compromise the security of applications using this package. This malicious code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue affects all versions starting from 0, making it critical for users to address it promptly.

How To Fix

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

npm uninstall glob-match

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

If you cannot update the package immediately, consider removing the glob-match dependency from your project until a secure version is available. You can do this by executing: npm uninstall glob-match.

Conclusion

The glob-match package has been identified to contain malicious code, posing a serious security risk to applications that utilize it. Users are strongly advised to update to the latest patched version or remove the package until it is secure. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for glob-match →

Share this vulnerability

FAQ

The glob-match package is used for matching file paths against glob patterns, facilitating file manipulation in JavaScript applications.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to use the Vulert playground without signup.

The malicious code in the glob-match package can lead to unauthorized access, data breaches, and other security incidents within your application.

Yes, a patched version of the glob-match package is available. You can update to the latest version using the command: npm update glob-match.

If immediate updates are not feasible, consider removing the glob-match dependency from your project until a secure version is available.

How To Fix

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

npm uninstall glob-match

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