MAL-2026-17485 Malicious code in css-scroll-anchor-polyfill (npm)
Malicious package
Published
MAL-2026-17485 is a malicious package: css-scroll-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-17485/ (Markdown: https://insights.sbomify.com/MAL-2026-17485/index.md)
- Package
- css-scroll-anchor-polyfill
- Registry
- npm
What is MAL-2026-17485?
MAL-2026-17485 is a malicious package in css-scroll-anchor-polyfill, published on 4 Oct 2026.
Official description
Package is published as css-scroll-anchor-polyfill but its index.js is empty and its contents impersonate internal Wix thunderbolt registry module names (thunderboltRegistry, siteAssetsRegistry, documentManagementRegistry, editorRegistry, corvidRegistry, and others) with a shipped registry-manifest.min.json mapping them to parastorage.com URLs. The declared purpose (a CSS scroll-anchor polyfill) is unrelated to the shipped code. thunderboltRegistry.js contains a top-level IIFE that executes on require: it runs local reconnaissance via child_process.execSync (cat /etc/hosts, whoami, id, pwd, ifconfig/ip addr, hostname, uname -a) and transmits the collected output together with a beacon (node version, process.platform, pid) via fetch to a hardcoded HTTP endpoint at http://dxpoc.gt.tc/callback.php/ef9ea0e191006f3cc6670720c99c26f3. Any internal build that resolves one of the impersonated thunderbolt names to this public package and requires the corresponding submodule triggers the reconnaissance and exfiltration path.
What should I do about MAL-2026-17485?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.