MAL-2026-17517 Malicious code in popover-anchor-polyfill (npm)
Malicious package
Published
MAL-2026-17517 is a malicious package: popover-anchor-polyfill (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-17517/ (Markdown: https://insights.sbomify.com/MAL-2026-17517/index.md)
- Package
- popover-anchor-polyfill
- Registry
- npm
What is MAL-2026-17517?
MAL-2026-17517 is a malicious package in popover-anchor-polyfill, published on 4 Oct 2026.
Official description
The package advertises itself as a 'popover anchor positioning polyfill' but ships thunderboltRegistry.js, which executes an IIFE on module load that spawns shell commands via child_process.execSync (
id, whoami, uname -a, ifconfig/ip addr) and reads /etc/hosts, then transmits each command's output together with hostname, Node version, platform, and pid over plain HTTP GET requests to the hardcoded endpoint http://dxpoc.gt.tc/callback.php/ef9ea0e191006f3cc6670720c99c26f3. The require path uses cache-bypass tricks (deleting require.cache entries matching 'thunderboltRegistry' and manually constructing a fresh Module to re-resolve child_process) to defeat mocking or interception. Sibling stub files and a registry-manifest.min.json impersonate Wix thunderbolt internal registry names (thunderboltRegistry, siteAssetsRegistry, documentManagementRegistry, editorRegistry, corvidRegistry) and reference static.parastorage.com, indicating a dependency-confusion lure targeting Wix build pipelines. The declared polyfill purpose does not match the shipped Wix-internal namespace exports, and no popover-polyfill functionality is implemented.What should I do about MAL-2026-17517?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.