Which versions of @posthog/rrweb are malicious?

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

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

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

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

Yes — @posthog/rrweb is associated with the GHSA-c37j-qh72-54w3 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 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 (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 across your stack and pipelines.

Malicious package

@posthog/rrwebnpm

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

MAL-2025-190673

Immediate action

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

npm uninstall @posthog/rrweb

What this malware does

The package @posthog/rrweb 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)

8278c73c0fa29817d8923864303d2e24c5a7bd038a9f8a2cae587329a3837cab

8e7ff62f7afccd552b5eff3833fa122ace1a2f8ef6447e4b372673896063098f

47b86bf336cedf6f91a8d7625488637e2b6c794bc6dd87380390f3723bcbfe93

a4d5c9fb8bfa73d4225eaa381816d0360bd0be5d566c631f24138c7b75d68528

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 (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 across your stack and pipelines.
If you installed it — respond
@posthog/rrweb 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 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 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 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-c37j-qh72-54w3

References

Credits

Amazon Inspector · finder

Detect & block this

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