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

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

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

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

If @posthog/rrweb-player 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 @posthog/rrweb-player across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @posthog/rrweb-player (version 0.0.31).

Part of a larger attack: @posthog published 56 malicious packages. See the full campaign →

Malicious package

@posthog/rrweb-playernpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

@posthog/rrweb-player is a confirmed malicious npm package (MAL-2025-190891) that steals credentials and exfiltrates sensitive data (malicious version 0.0.31). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @posthog/rrweb-player (npm)

MAL-2025-190891

Immediate action

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

npm uninstall @posthog/rrweb-player

What this malware does

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

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)

7d82edc82839a426c18772dee75ba0a7a9601a053fa6a20b3e7e4b48ac3768d9

2f9939b2bfb450c5cfd34b7a992195a3bfb2c87b6f56f1c342a70c5b2c1e4acb

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @posthog/rrweb-player (version 0.0.31).
If you installed it — respond
@posthog/rrweb-player 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-player 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. @posthog/rrweb-player 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.

References

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database