MAL-2026-17555 Malicious code in css-nbanqq-polyfill (npm)
Malicious package
Published
MAL-2026-17555 is a malicious package: css-nbanqq-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-17555/ (Markdown: https://insights.sbomify.com/MAL-2026-17555/index.md)
- Package
- css-nbanqq-polyfill
- Registry
- npm
What is MAL-2026-17555?
MAL-2026-17555 is a malicious package in css-nbanqq-polyfill, published on 5 Oct 2026.
Official description
The package impersonates Wix thunderbolt internal registry modules (exporting
thunderboltRegistry, siteAssetsRegistry, editorRegistry, corvidRegistry, etc. and shipping a registry-manifest.min.json referencing static.parastorage.com) as a dependency-confusion lure. On require of thunderboltRegistry.js, a top-level IIFE uses child_process.execSync to run id, whoami, uname -a, ifconfig/ip addr, and cat /etc/hosts, URL-encodes the output together with hostname, Node version, platform, and pid, and sends it via fetch to the hardcoded attacker endpoint http://dxpoc.gt.tc/callback.php/bb8968d0f67000433bf7005dd5ad2d1f. Proxy-wrapped stubs make the require() call appear to resolve normally while the exfiltration runs. Any build or runtime that resolves this package name will execute the reconnaissance payload and leak host identity and network configuration to the attacker-controlled host.What should I do about MAL-2026-17555?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.