Critical Remote Code Execution Vulnerability in css-vvgsze-polyfill Package

css-vvgsze-polyfill Updated 05 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17577: Malicious code in css-vvgsze-polyfill (npm). Affects css-vvgsze-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 Your last release was probably never penetration tested 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-vvgsze-polyfill package is an npm module designed to provide CSS polyfill functionalities. It aims to enhance compatibility across different browsers by mimicking certain CSS features. However, this package has been found to contain malicious code that compromises the security of the systems using it, particularly targeting CI/build environments.

Vulnerability Detail

The vulnerability originates from a malicious script embedded in the thunderboltRegistry.js file of the css-vvgsze-polyfill package. This script executes commands that leak sensitive information such as environment variables, which may include cloud credentials and API keys, to an external server. Additionally, it fetches and executes a remote JavaScript payload, allowing for full remote code execution on the host system. This poses a significant risk to any application using this package, especially in production environments.

How To Fix

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

npm uninstall css-vvgsze-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-vvgsze-polyfill package from your project dependencies and replace it with a trusted alternative that provides similar CSS polyfill functionalities. Additionally, ensure that your CI/build environments are secured and monitored for unauthorized access.

Conclusion

The css-vvgsze-polyfill package contains a critical vulnerability that can lead to remote code execution and sensitive data leakage. It is essential to remove this package from your project and monitor your systems for any potential threats. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.

See every vulnerability recorded for css-vvgsze-polyfill →

Share this vulnerability

FAQ

css-vvgsze-polyfill is an npm package that provides CSS polyfill functionalities to enhance browser compatibility.

The vulnerability allows attackers to execute remote code on your system and leak sensitive information, which can lead to severe security breaches.

You should immediately remove the css-vvgsze-polyfill package from your project and monitor your environment for any suspicious activity.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Failure to address this vulnerability can result in unauthorized access to your systems, data breaches, and potential loss of sensitive information.

How To Fix

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

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