Which versions of org.mvnpm:posthog-node are malicious?

The following Maven versions of org.mvnpm:posthog-node are flagged malicious: 4.18.1. Treat any of these as compromised.

How do I remediate org.mvnpm:posthog-node if I installed it?

org.mvnpm:posthog-node 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 org.mvnpm:posthog-node — how do I know if it already compromised me?

If org.mvnpm:posthog-node 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 org.mvnpm:posthog-node across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for org.mvnpm:posthog-node (version 4.18.1).

Malicious package

org.mvnpm:posthog-nodeMaven

Advisory published Nov 26, 2025Updated Nov 26, 2025

org.mvnpm:posthog-node is a confirmed malicious Maven package (MAL-2025-191470) that steals credentials and exfiltrates sensitive data (malicious version 4.18.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in org.mvnpm:posthog-node (Maven)

MAL-2025-191470

Immediate action

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

remove org.mvnpm:posthog-node

What this malware does

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

4.18.1

Indicators of compromise (SHA-256)

ea90a5928d7667bed4fa9f6effbbe6c8d3ad6521ca51ca2b01551bc02373a7d2

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for org.mvnpm:posthog-node (version 4.18.1).
If you installed it — respond
org.mvnpm:posthog-node 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 org.mvnpm:posthog-node 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. org.mvnpm:posthog-node on Maven has been identified as a malicious package (version 4.18.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Detect & block this

O3 blocks org.mvnpm:posthog-node-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