Which versions of posthog-react-native are malicious?

The following npm versions of posthog-react-native are flagged malicious: 4.11.1, 4.12.5. Treat any of these as compromised.

How do I remediate posthog-react-native if I installed it?

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

If posthog-react-native 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-react-native across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for posthog-react-native (2 malicious versions).

Malicious package

posthog-react-nativenpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

posthog-react-native is a confirmed malicious npm package (MAL-2025-190926) that steals credentials and exfiltrates sensitive data (malicious versions 4.11.1, 4.12.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in posthog-react-native (npm)

MAL-2025-190926

Immediate action

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

npm uninstall posthog-react-native

What this malware does

The package posthog-react-native 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

2 flagged

4.11.14.12.5

Indicators of compromise (SHA-256)

bdc429049d0797390f57bc821cabd2d46fad88c5363136fc96bab4b5497000fe

3750278ea88edf0ebcf86392fa3a9179766a1a65004bb33e995c2f627883785e

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for posthog-react-native (2 malicious versions).
If you installed it — respond
posthog-react-native 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-react-native 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-react-native on npm has been identified as a malicious package (versions 4.11.1, 4.12.5 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-react-native-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