Which versions of rrweb-v1 are malicious?

The following npm versions of rrweb-v1 are flagged malicious: 99.99.2. Treat any of these as compromised.

How do I remediate rrweb-v1 if I installed it?

Remove rrweb-v1 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 rrweb-v1 — how do I know if it already compromised me?

If rrweb-v1 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.

How do I find rrweb-v1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rrweb-v1 (version 99.99.2).

Malicious package

rrweb-v1npm

Advisory published Mar 13, 2026Updated Mar 23, 2026

rrweb-v1 is a confirmed malicious npm package (MAL-2026-1456) that executes malicious code on install (malicious version 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rrweb-v1 (npm)

MAL-2026-1456

Immediate action

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

npm uninstall rrweb-v1

What this malware does

The package rrweb-v1 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'rrweb-v1' @ 99.99.2 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.99.2

Indicators of compromise (SHA-256)

94ad4f38fe1502fe61c2de51dac1c4e4c569535af81a38c6b2af57e4bd26b16c

b2c1a8d89ba0817d9264bc9f6e59c5c1e4c683b98ce32ba7d9bcb3e61f1f016b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for rrweb-v1 (version 99.99.2).
If you installed it — respond
Remove rrweb-v1 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 rrweb-v1 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. rrweb-v1 on npm has been identified as a malicious package (version 99.99.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks rrweb-v1-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