css-hgwctv-polyfillnpm
Advisory published Updated
css-hgwctv-polyfill is a confirmed malicious npm package (MAL-2026-17552) 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-hgwctv-polyfill (npm)
What this malware does
On require, thunderboltRegistry.js runs an immediately-invoked function that uses child_process.execSync to collect host identity and network reconnaissance from the installer's machine (id, whoami, uname -a, ifconfig/ip addr, and /etc/hosts), plus hostname, Node.js version, platform and pid, and transmits each result via fetch to the hardcoded plain-HTTP endpoint http://dxpoc.gt.tc/callback.php/bb8968d0f67000433bf7005dd5ad2d1f. The package also exports Proxy stubs named thunderboltRegistry, siteAssetsRegistry, editorRegistry, corvidRegistry and ships a registry-manifest.min.json referencing parastorage.com, mimicking internal Wix thunderbolt build modules so the module auto-loads inside a Wix build and executes the reconnaissance payload. A CSS polyfill has no functional reason to execute shell commands, read /etc/hosts, or contact an external host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for css-hgwctv-polyfill (version 1.0.0).
If you installed it — respond
css-hgwctv-polyfill is a typosquat — you almost certainly intended a legitimately-named package. Remove css-hgwctv-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-hgwctv-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks css-hgwctv-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.