Critical Malicious Code Vulnerability in css-gvqmfn-polyfill Package

css-gvqmfn-polyfill Updated 05 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17551: Malicious code in css-gvqmfn-polyfill (npm). Affects css-gvqmfn-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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The css-gvqmfn-polyfill package is an npm library designed to mimic the internal CSS polyfill naming conventions used by Wix. It aims to provide compatibility and functionality for various Wix-related projects. However, this package has been identified as containing malicious code that can compromise the security of applications utilizing it.

Vulnerability Detail

The vulnerability originates from a malicious implementation within the css-gvqmfn-polyfill package. When the thunderboltRegistry.js file is required, it executes a series of commands that collect sensitive system information, such as the hostname, Node version, platform, and process ID. This data is then sent to a hardcoded attacker endpoint over plain HTTP, posing a significant risk of remote code execution (RCE) and data leakage. The package also employs a deceptive mechanism by re-exporting registry names as no-op functions, making it appear functional while executing malicious activities.

How To Fix

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

npm uninstall css-gvqmfn-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 remove the css-gvqmfn-polyfill package from your project to mitigate the risk of exploitation. This can be done by executing the following command:

npm uninstall css-gvqmfn-polyfill

Additionally, monitor your application using Vulert, which can alert you in real-time for open-source vulnerabilities without requiring code access or installation.

Conclusion

The css-gvqmfn-polyfill package contains a critical vulnerability that can lead to remote code execution and data leakage. It is essential to update or remove the package to protect your application. Utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for css-gvqmfn-polyfill →

Share this vulnerability

FAQ

css-gvqmfn-polyfill is an npm package that mimics Wix's internal CSS polyfill naming conventions to provide compatibility for Wix-related projects.

The vulnerability allows malicious code to execute commands on your system, potentially leading to data leakage and remote code execution.

Check the npm registry for updates to the css-gvqmfn-polyfill package. If a patched version is available, update your package to mitigate the risk.

You can use Vulert to monitor your application for open-source vulnerabilities in real-time. It requires only the package-lock.json file and no installation.

If no patched version is available, consider removing the css-gvqmfn-polyfill package from your dependencies until a secure version is released.

How To Fix

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

npm uninstall css-gvqmfn-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