polypromptnpm
Advisory published Updated
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for polyprompt (version 1.0.0).
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 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
Campaign
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.