Which versions of @posthog/rrdom are malicious?

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

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

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

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

Yes — @posthog/rrdom is associated with the GHSA-r8fm-xf88-xm57 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/rrdom 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/rrdom (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/rrdom across your stack and pipelines.

Malicious package

@posthog/rrdomnpm

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

MAL-2025-190672

Immediate action

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

npm uninstall @posthog/rrdom

What this malware does

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

6ad32d1af00f220489835e70f37db33a18034db715e2b750dc95639ba7e05d75

b58f6a4822c61ea47436ea08eeb6ab0f8083fd7fed7ea3c2c42a832ab84a57ba

99629493d8795d26d370a91fe9caf61b257de03e11fc8a140740b0d1a1c3a0ca

241caaf703385a583d1fa60268e62d0a56e92eac7f42ecaaf5cf4b68e5b9bfbc

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/rrdom (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/rrdom across your stack and pipelines.
If you installed it — respond
@posthog/rrdom 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/rrdom 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/rrdom 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/rrdom 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-r8fm-xf88-xm57

References

Credits

Amazon Inspector · finder

Detect & block this

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