# MAL-2026-11476: Malicious code in polyprompt (npm)


- **Type:** Malicious package
- **Package:** `polyprompt` (npm)
- **Published:** 31 Jul 2026
- **Also known as:** GHSA-h574-ghq2-gh4p

## What is MAL-2026-11476?

MAL-2026-11476 is a malicious package in polyprompt, published on 31 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-11476?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11476 is a malicious package: polyprompt (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11476/ (Markdown: https://insights.sbomify.com/MAL-2026-11476/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11476

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11476/
Summaries are generated and may contain mistakes; the official description above is the record.