Which versions of polyprompt are malicious?

The following npm versions of polyprompt are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate polyprompt if I installed it?

polyprompt 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 polyprompt — how do I know if it already compromised me?

If polyprompt 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 polyprompt part of a known attack campaign?

Yes — polyprompt is associated with the GHSA-h574-ghq2-gh4p, IN-MAL-2026-012921 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 polyprompt 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 polyprompt (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polyprompt across your stack and pipelines.

Malicious package

polypromptnpm

polyprompt is a confirmed malicious npm package (MAL-2026-11476) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in polyprompt (npm)

MAL-2026-11476

Immediate action

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

npm uninstall polyprompt

What this malware does

lib/report.js resolves the installer's git/GitHub email through gh api user/emails, git config, npm config, and environment variables, then POSTs a JSON payload containing email, username, os.hostname(), a run counter, and the package name to a hardcoded Zapier webhook at https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. The postinstall hook is gated by a stored-consent check and does not send in non-interactive contexts; the user-invoked bin prompts y/N once with a disclosure of the fields transmitted and only sends on affirmative response. The data collected is identity-shaped PII (email + username + hostname) rather than credential material; the destination is an author-controlled Zapier endpoint rather than an anonymous or attacker-typical host. No environment scraping, credential-path reads (~/.aws, ~/.ssh, ~/.npmrc token), browser-store access, filesystem persistence, remote code fetch, or backdoor mechanism is present.

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c83b81c4da433d42ff97456ac6c52970f52de665ee78be41fd4c4ee34705adf2

52da21b792fba3cc472cb67f1a5b445786802d67b6cf81b45409acdab8724c17

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

Campaign

GHSA-h574-ghq2-gh4pIN-MAL-2026-012921

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks polyprompt-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