# MAL-2026-10099: Malicious code in polipoli-pak (npm)


- **Type:** Malicious package
- **Package:** `polipoli-pak` (npm)
- **Published:** 9 Jul 2026
- **Also known as:** GHSA-9rgw-9wxh-3pp2

## What is MAL-2026-10099?

MAL-2026-10099 is a malicious package in polipoli-pak, published on 9 Jul 2026. 

### Official description

On npm install, postinstall.js runs automatically and performs two unauthorized actions against the installer. First, it POSTs a JSON fingerprint of the installing machine — os.hostname(), os.userInfo().username, platform, arch, node version, cwd, INIT_CWD, npm user-agent, and the sorted list of every process.env variable name — to a hardcoded webhook.site canary URL (https://webhook.site/a428f027-90c9-45e2-acca-ffbb4ea86044) that the installer never configured. Second, it walks common project locations under INIT_CWD (index.html, public/index.html, src/index.html, dist/index.html, build/index.html) and rewrites each file via fs.writeFileSync to inject a fixed-position red banner div into the page body. The environment-variable name inventory reveals which credentials are present on the host, and the HTML rewrite silently modifies files the installer owns at install time.

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-10099?

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-10099 is a malicious package: polipoli-pak (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-10099/ (Markdown: https://insights.sbomify.com/MAL-2026-10099/index.md)
```

## Sources

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

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