Which versions of path-to-regexp-updated are malicious?

The following npm versions of path-to-regexp-updated are flagged malicious: 99.99.1, 99.99.2. Treat any of these as compromised.

How do I remediate path-to-regexp-updated if I installed it?

Remove path-to-regexp-updated from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If path-to-regexp-updated was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is path-to-regexp-updated part of a known attack campaign?

Yes — path-to-regexp-updated is associated with the RLMA-2026-01477 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 path-to-regexp-updated across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for path-to-regexp-updated (2 malicious versions).

Malicious package

path-to-regexp-updatednpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

path-to-regexp-updated is a confirmed malicious npm package (MAL-2026-1808) that executes malicious code on install (malicious versions 99.99.1, 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in path-to-regexp-updated (npm)

MAL-2026-1808

Immediate action

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

npm uninstall path-to-regexp-updated

What this malware does

The package path-to-regexp-updated was found to contain malicious code.

Malicious versions

2 flagged

99.99.199.99.2

Indicators of compromise (SHA-256)

7e9b182f73651ab54954f6beeec3794607fa5a4bc485daded6532b0bbb0bdbf6

d4f886299ed0f104de3331f447c127332d6de7b5d3bff5954553bb5c50099dfc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for path-to-regexp-updated (2 malicious versions).
If you installed it — respond
Remove path-to-regexp-updated from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If path-to-regexp-updated was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. path-to-regexp-updated on npm has been identified as a malicious package (versions 99.99.1, 99.99.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01477

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks path-to-regexp-updated-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database