Malicious code in polipoli-pak (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (a8693677ff1f1f887c11d3b4f6ad3f1742c7eefd07b6b8cfabd6cfccc32bc48f) 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. ## Source: ghsa-malware (ee2266f117d4745534d3257b98734ddfbeb31634bbbc4b3b0de9a2dee97d4e07) 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.
AI Analysis
Technical Summary
The polipoli-pak package versions 1.0.1 and 1.0.2 include a postinstall.js script that runs automatically on npm install. This script performs two unauthorized actions: it sends a JSON fingerprint of the installer's environment—including hostname, username, platform, architecture, Node.js version, current working directory, npm user-agent, and environment variable names—to a hardcoded webhook.site URL. It also searches for common index.html files in the project directory and overwrites them to inject a fixed-position red banner div into the page body. This behavior exposes sensitive environment information and modifies user project files without consent.
Potential Impact
The unauthorized exfiltration of environment details can reveal sensitive information about the host system and credentials present in environment variables. The silent modification of HTML files can disrupt project integrity and introduce unwanted visual elements, potentially impacting application behavior or user trust. Although no known exploits in the wild are reported, the presence of this malicious code poses a significant risk to confidentiality and integrity of the affected projects.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing polipoli-pak versions 1.0.1 and 1.0.2. Review and remove these versions from projects if present. Monitor for updates or advisories from the package maintainers or npm registry. Since this is not a cloud service, remediation depends on user action to uninstall or replace the malicious package. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for current remediation guidance.
Malicious code in polipoli-pak (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (a8693677ff1f1f887c11d3b4f6ad3f1742c7eefd07b6b8cfabd6cfccc32bc48f) 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. ## Source: ghsa-malware (ee2266f117d4745534d3257b98734ddfbeb31634bbbc4b3b0de9a2dee97d4e07) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The polipoli-pak package versions 1.0.1 and 1.0.2 include a postinstall.js script that runs automatically on npm install. This script performs two unauthorized actions: it sends a JSON fingerprint of the installer's environment—including hostname, username, platform, architecture, Node.js version, current working directory, npm user-agent, and environment variable names—to a hardcoded webhook.site URL. It also searches for common index.html files in the project directory and overwrites them to inject a fixed-position red banner div into the page body. This behavior exposes sensitive environment information and modifies user project files without consent.
Potential Impact
The unauthorized exfiltration of environment details can reveal sensitive information about the host system and credentials present in environment variables. The silent modification of HTML files can disrupt project integrity and introduce unwanted visual elements, potentially impacting application behavior or user trust. Although no known exploits in the wild are reported, the presence of this malicious code poses a significant risk to confidentiality and integrity of the affected projects.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing polipoli-pak versions 1.0.1 and 1.0.2. Review and remove these versions from projects if present. Monitor for updates or advisories from the package maintainers or npm registry. Since this is not a cloud service, remediation depends on user action to uninstall or replace the malicious package. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10099
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba4c68715ace4357ea4a
Added to database: 07/10/2026, 09:24:28 UTC
Last enriched: 07/10/2026, 09:38:51 UTC
Last updated: 07/29/2026, 18:26:45 UTC
Views: 27
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.