Which versions of css-nbanqq-polyfill are malicious?

The following npm versions of css-nbanqq-polyfill are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate css-nbanqq-polyfill if I installed it?

css-nbanqq-polyfill is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed css-nbanqq-polyfill — how do I know if it already compromised me?

If css-nbanqq-polyfill was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is css-nbanqq-polyfill part of a known attack campaign?

Yes — css-nbanqq-polyfill is associated with the IN-MAL-2026-021015 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find css-nbanqq-polyfill across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for css-nbanqq-polyfill (version 1.0.0).

Malicious package

css-nbanqq-polyfillnpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

css-nbanqq-polyfill is a confirmed malicious npm package (MAL-2026-17555) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in css-nbanqq-polyfill (npm)

MAL-2026-17555

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall css-nbanqq-polyfill

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7377a70c94f8fd1719147b2023860926935a70410f672e07411326284f11a69f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for css-nbanqq-polyfill (version 1.0.0).
If you installed it — respond
css-nbanqq-polyfill is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If css-nbanqq-polyfill was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. css-nbanqq-polyfill on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021015

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks css-nbanqq-polyfill-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database