Malicious Code Injection in css-a11y-contrast-utils: A Critical Vulnerability

css-a11y-contrast-utils Updated 05 Oct 2026

Summary

04/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17475: Malicious code in css-a11y-contrast-utils (npm). Affects css-a11y-contrast-utils 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

css-a11y-contrast-utils is an npm package designed to assist developers in ensuring compliance with WCAG contrast standards. However, the version 1.0.0 of this package has been found to contain no actual contrast utility code. Instead, it exports an empty object and includes a Proxy that exposes identifiers from Wix's internal registry, making it a target for dependency confusion attacks.

Vulnerability Detail

The vulnerability originates from the malicious design of the css-a11y-contrast-utils package, which masquerades as a legitimate utility while executing harmful code upon loading. Specifically, it runs an IIFE that collects sensitive system information such as hostname, user ID, kernel version, Node version, and process ID. This data is then exfiltrated through DNS lookups and HTTP requests to hardcoded external servers, posing significant security risks to users who install this package.

How To Fix

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

npm uninstall css-a11y-contrast-utils

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 measure, avoid using the css-a11y-contrast-utils package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The css-a11y-contrast-utils package has been identified as containing malicious code that poses significant security risks. Users are advised to uninstall the package immediately and consider alternatives. Continuous monitoring for vulnerabilities is crucial to maintaining application security.

See every vulnerability recorded for css-a11y-contrast-utils →

Share this vulnerability

FAQ

css-a11y-contrast-utils is an npm package intended to help developers ensure compliance with WCAG contrast standards.

The vulnerability allows malicious code to run on your system, potentially exfiltrating sensitive information and compromising your application's security.

Immediately uninstall the css-a11y-contrast-utils package and monitor your system for any unusual activity.

Yes, consider using other well-reviewed packages that provide WCAG contrast utilities without the security risks.

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

How To Fix

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

npm uninstall css-a11y-contrast-utils

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