Which versions of @posthog/rrweb-record are malicious?

The following npm versions of @posthog/rrweb-record are flagged malicious: 0.0.31. Treat any of these as compromised.

How do I remediate @posthog/rrweb-record if I installed it?

@posthog/rrweb-record 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 @posthog/rrweb-record — how do I know if it already compromised me?

If @posthog/rrweb-record 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 @posthog/rrweb-record part of a known attack campaign?

Yes — @posthog/rrweb-record is associated with the GHSA-m235-pcqr-5x5g 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 @posthog/rrweb-record 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 @posthog/rrweb-record (version 0.0.31). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @posthog/rrweb-record across your stack and pipelines.

Malicious package

@posthog/rrweb-recordnpm

Malicious code in @posthog/rrweb-record (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190752

Immediate action

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

npm uninstall @posthog/rrweb-record

What this malware does

The package @posthog/rrweb-record was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.0.31

Indicators of compromise (SHA-256)

07e9e0d187bd09bd0a23bdbf5b1b1708abe7a60bf5b3e96a532f1363e239e6be

19ff125dfd13ba489699b36ca14acbab8e87eda739d43d9a31ef2a3a59903398

922282c167cbf9eb9914018231b02e208f47099e7fe37e470f5b0fd265fcf986

b61a25ea0c59751439b8acbfde1e5cfc100fa6f0c73e72cf773f568a40603d85

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 @posthog/rrweb-record (version 0.0.31). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @posthog/rrweb-record across your stack and pipelines.
If you installed it — respond
@posthog/rrweb-record 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 @posthog/rrweb-record 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 @posthog/rrweb-record 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. @posthog/rrweb-record on npm has been identified as a malicious package (version 0.0.31 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m235-pcqr-5x5g

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @posthog/rrweb-record-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