Which versions of @posthog/plugin-contrib are malicious?

The following npm versions of @posthog/plugin-contrib are flagged malicious: 0.0.6. Treat any of these as compromised.

How do I remediate @posthog/plugin-contrib if I installed it?

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

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

Yes — @posthog/plugin-contrib is associated with the GHSA-g7v2-2xxc-c78j 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/plugin-contrib 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/plugin-contrib (version 0.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @posthog/plugin-contrib across your stack and pipelines.

Malicious package

@posthog/plugin-contribnpm

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

MAL-2025-190751

Immediate action

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

npm uninstall @posthog/plugin-contrib

What this malware does

The package @posthog/plugin-contrib 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.6

Indicators of compromise (SHA-256)

e7be7c80e1b4ff3df4c7d2b1129e9b889b217c95c62bb2e4623165db643e488e

afcd017c0dad0f7c8771c40b6fbc9308cf19b77a704f62856696156fb3cf156b

1651ff1aae98d06c4276b3177a78fa4acb41c236199a920ae929935cfa557c76

613c0aad1ec62f4d0d7ff6a88c66428574f2bb1b9382b58e279982e9e802d4dd

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/plugin-contrib (version 0.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @posthog/plugin-contrib across your stack and pipelines.
If you installed it — respond
@posthog/plugin-contrib 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/plugin-contrib 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/plugin-contrib 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/plugin-contrib on npm has been identified as a malicious package (version 0.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g7v2-2xxc-c78j

References

Credits

Amazon Inspector · finder

Detect & block this

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