Critical Malicious Code Vulnerability in css-eqxcdx-polyfill Package

css-eqxcdx-polyfill Updated 05 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17573: Malicious code in css-eqxcdx-polyfill (npm). Affects css-eqxcdx-polyfill versions 1.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The css-eqxcdx-polyfill package is designed to provide polyfill functionalities for web applications, specifically exporting registry stubs related to Wix's Thunderbolt framework. However, this package has been found to contain malicious code that compromises the security of the host environment.

Vulnerability Detail

The vulnerability originates from the package's thunderboltRegistry.js file, which executes an Immediately Invoked Function Expression (IIFE) upon module load. This IIFE performs two malicious actions: it collects sensitive information such as the OS hostname and environment variables, then sends this data to a hardcoded external server. Additionally, it executes a remote Python payload via curl, leading to potential remote code execution. This poses significant risks, including exposure of sensitive credentials and unauthorized access to the host system.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall css-eqxcdx-polyfill

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can prevent the execution of the malicious code by avoiding the installation of the css-eqxcdx-polyfill package. If it is already installed, you should uninstall it using the command: npm uninstall css-eqxcdx-polyfill.

Conclusion

The css-eqxcdx-polyfill package contains a critical vulnerability that exposes systems to malicious code execution and sensitive data leakage. Immediate action is required to mitigate risks by uninstalling the package and monitoring for any unauthorized access.

See every vulnerability recorded for css-eqxcdx-polyfill →

Share this vulnerability

FAQ

The css-eqxcdx-polyfill package is intended to provide polyfill functionalities for web applications, specifically related to Wix's Thunderbolt framework.

The vulnerability can lead to the exposure of sensitive information, such as environment variables and credentials, and may allow unauthorized remote code execution on your system.

You should immediately uninstall the css-eqxcdx-polyfill package and monitor your system for any suspicious activity.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall css-eqxcdx-polyfill

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback