Which versions of @posthog/clickhouse are malicious?

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

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

@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.

I already installed @posthog/clickhouse — how do I know if it already compromised me?

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

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

Malicious package

@posthog/clickhousenpm

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

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @posthog/clickhouse (version 1.7.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @posthog/clickhouse across your stack and pipelines.
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.
Did it already run?
If @posthog/clickhouse 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/clickhouse 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/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