Which versions of glob-to-regexp are malicious?

The following PyPI versions of glob-to-regexp are flagged malicious: 2.1.1. Treat any of these as compromised.

How do I remediate glob-to-regexp if I installed it?

glob-to-regexp is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed glob-to-regexp — how do I know if it already compromised me?

If glob-to-regexp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is glob-to-regexp part of a known attack campaign?

Yes — glob-to-regexp is associated with the RLMA-2025-03601, GENERIC-questionable-pentest, RLUA-2026-00354 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find glob-to-regexp across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for glob-to-regexp (version 2.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging glob-to-regexp across your stack and pipelines.

Malicious package

glob-to-regexpPyPI

Malicious code in glob-to-regexp (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6510

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall glob-to-regexp

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

1 flagged

2.1.1

Indicators of compromise (SHA-256)

b31da7c7fd7ad49ca8a9405ced3e86110db1d009d5c81b86b43d4b3ecf9c07f6

cf30ef4509936adbb986886d9c78944b3b479b6bbdbf5eb7229e05cc34b94d1c

ce8e1c3de8370811f29db098c2ca6d1fbd027017b5e29a9b540a3dbe8f58c704

02363deb3264955f06243b8df87b2198cf339eabd74b238d2c13c5023e1fcc89

48372e32eed896c82ce0275448fdb081d9f6bd7d20b4d947011cf7882da2293e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for glob-to-regexp (version 2.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging glob-to-regexp across your stack and pipelines.
If you installed it — respond
glob-to-regexp is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If glob-to-regexp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks glob-to-regexp before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. glob-to-regexp on PyPI has been identified as a malicious package (version 2.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03601GENERIC-questionable-pentestRLUA-2026-00354

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks glob-to-regexp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring