NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @posthog published 56 malicious packages. See the full campaign →
Malicious package

@posthog/clickhousenpm

Advisory published Updated

@posthog/clickhouse is a confirmed malicious npm package (MAL-2025-190945) that steals credentials and exfiltrates sensitive data (malicious version 1.7.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @posthog/clickhouse (npm)

MAL-2025-190945
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @posthog/clickhouse

What this malware does

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

Indicators of compromise (SHA-256)

feeaa10a864684274d993ef940dd92cdcda023ba75680588c31f515eca5d0afe
ab67710c7cf24d338618be2ab087d4c3b27117879492e29334b31cd0328e171a
0c2e2871faa55dcedc21bb4e212b945597d00a05e3de96ddacdd68d1740fe5b7

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @posthog/clickhouse (version 1.7.1).

  2. If you installed it — respond

    @posthog/clickhouse 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.

  3. Did it already run?

    If @posthog/clickhouse 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/clickhouse on npm has been identified as a malicious package (version 1.7.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h33f-hhfm-c5wv

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @posthog/clickhouse-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
@posthog/clickhouse (npm) malicious package — MAL-2025-190945 | O3 Security