Which versions of @posthog/wizard are malicious?

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

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

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

If @posthog/wizard 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 @posthog/wizard across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @posthog/wizard (version 1.18.1).

Part of a larger attack: @posthog published 56 malicious packages. See the full campaign →

Malicious package

@posthog/wizardnpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

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

Malicious code in @posthog/wizard (npm)

MAL-2025-190900

Immediate action

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

npm uninstall @posthog/wizard

What this malware does

The package @posthog/wizard was found to contain malicious code.

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

Indicators of compromise (SHA-256)

43ed05e891884ed2cf2d6f1790352cd3d07f97a03c6fb152561eb2e8b9d938c2

000f34cfeb0580c5bca4b27313e006b9e5fa8a897ebda844fa7ce1832520cf08

Detection & response playbook

Credential / info stealer

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

References

Credits

Amazon Inspector · finder

Detect & block this

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