Which versions of css-kfvwax-polyfill are malicious?

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

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

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

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

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

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

Malicious package

css-kfvwax-polyfillnpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

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

MAL-2026-17575

Immediate action

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

npm uninstall css-kfvwax-polyfill

What this malware does

On require(), thunderboltRegistry.js runs an IIFE that shells out via child_process to collect host identity (id, whoami, uname -a), network interface listings (ifconfig/ip addr), and the contents of /etc/hosts, together with the machine hostname and a beacon containing Node version, platform, and pid. The collected output is sent via fetch to the hardcoded URL https://unl9pgk6ei4uf80n5tf4iktspjvbuzkn9.oastify.com/ (Burp Collaborator OAST). The module also exports a Proxy mimicking Wix thunderbolt registry APIs (ensureComponentLoadersAreCreated, loadComponents, etc.) under namespaces such as thunderboltRegistry, siteAssetsRegistry, documentManagementRegistry, and editorRegistry, acting as a cover-story API shape consistent with a dependency-confusion or typosquat payload against Wix internal tooling. Installing or importing this package causes host reconnaissance data to be exfiltrated to attacker-controlled infrastructure.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2041e61cd16558aaaeac8a2f26024866a6b949d93817f78de744c5c1781023df

Detection & response playbook

Credential / info stealer

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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