Which versions of css-svqggc-polyfill are malicious?

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

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

css-svqggc-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-svqggc-polyfill — how do I know if it already compromised me?

If css-svqggc-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-svqggc-polyfill part of a known attack campaign?

Yes — css-svqggc-polyfill is associated with the IN-MAL-2026-021023 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-svqggc-polyfill across my projects, lockfiles, and CI pipelines?

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

Malicious package

css-svqggc-polyfillnpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

css-svqggc-polyfill is a confirmed malicious npm package (MAL-2026-17557) 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-svqggc-polyfill (npm)

MAL-2026-17557

Immediate action

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

npm uninstall css-svqggc-polyfill

What this malware does

Package masquerades as a CSS polyfill while impersonating internal Wix Thunderbolt registry modules (thunderboltRegistry, siteAssetsRegistry, editorRegistry, corvidRegistry, and other namespace stubs), with a shipped registry-manifest pointing those names at parastorage.com URLs under this package's own name — a dependency-confusion shape. thunderboltRegistry.js runs an IIFE on require that purges its own entries from require.cache so each require re-runs the payload, obtains child_process via multiple fallbacks (including constructing a fresh Module instance to bypass sandboxed require stubs), and executes reconnaissance commands (id, whoami, uname -a, ifconfig/ip addr, /etc/hosts) via execSync. The command output plus host beacon fields (node version, platform, pid, hostname, site) are sent over cleartext HTTP via fetch GET to the hardcoded endpoint http://dxpoc.gt.tc/callback.php/bb8968d0f67000433bf7005dd5ad2d1f. The Proxy-based stub exports ensure the import appears to succeed silently after exfiltration.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6b23cf39720388bcf9f26621bd52e256e18a011bf3b6821b7d9f5f60115b9663

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for css-svqggc-polyfill (version 1.0.0).
If you installed it — respond
css-svqggc-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-svqggc-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-svqggc-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-021023

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks css-svqggc-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