Which versions of css-dwsawd-polyfill are malicious?

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

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

css-dwsawd-polyfill is a typosquat — you almost certainly intended a legitimately-named package. Remove css-dwsawd-polyfill, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

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

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

Malicious package

css-dwsawd-polyfillnpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

css-dwsawd-polyfill is a confirmed malicious npm package (MAL-2026-17550) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in css-dwsawd-polyfill (npm)

MAL-2026-17550

Immediate action

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

npm uninstall css-dwsawd-polyfill

What this malware does

The package name mimics a Wix thunderbolt polyfill and ships a registry-manifest.min.json that aliases legitimate @wix thunderbolt registry module names to thunderboltRegistry.js. On require, thunderboltRegistry.js runs an IIFE that uses child_process.execSync to execute shell reconnaissance (id, whoami, uname -a, ifconfig/ip addr, /etc/hosts) and fetches http://dxpoc.gt.tc/callback.php/bb8968d0f67000433bf7005dd5ad2d1f with the command outputs plus hostname, pid, platform, node version, and a site identifier as query parameters, tagged 'rce-poc'. A fallback path constructs a fresh Module instance to re-resolve child_process if the require cache is stubbed, ensuring execution. The destination is plain HTTP to an unrelated external host and is not caller-configurable.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1c370cda09695e44d06a44bc14d14817edadc047e4dad0314edcfc752be796e9

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for css-dwsawd-polyfill (version 1.0.0).
If you installed it — respond
css-dwsawd-polyfill is a typosquat — you almost certainly intended a legitimately-named package. Remove css-dwsawd-polyfill, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If css-dwsawd-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-dwsawd-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-021014

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks css-dwsawd-polyfill-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database