Which versions of @posthog/ai are malicious?

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

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

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

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

Yes — @posthog/ai is associated with the GHSA-mjv6-3w2m-7669 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/ai 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/ai (version 7.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @posthog/ai across your stack and pipelines.

Malicious package

@posthog/ainpm

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

MAL-2025-190644

Immediate action

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

npm uninstall @posthog/ai

What this malware does

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

7.1.2

Indicators of compromise (SHA-256)

1e6a08419969270cca059f804bb3ec25aa0427f00ef555a9409c12d50921a83c

0a9a022b20b3025cb0846139ab6f2a1308025ed8ee902db18aacbfa95c6ea7e6

a86c420bea28c0865168974625af9f2fb863f8eff8e986e9f59d26cbc735cb29

7120d00d5f1e13ba8c718d91d15c19a4cfe770b4e2fb00dbac8d8c9ea32844e4

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

Campaign

GHSA-mjv6-3w2m-7669

References

Credits

Amazon Inspector · finder

Detect & block this

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