MAL-2026-17475 Malicious code in css-a11y-contrast-utils (npm)
Malicious package
Published
MAL-2026-17475 is a malicious package: css-a11y-contrast-utils (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-17475/ (Markdown: https://insights.sbomify.com/MAL-2026-17475/index.md)
- Package
- css-a11y-contrast-utils
- Registry
- npm
What is MAL-2026-17475?
MAL-2026-17475 is a malicious package in css-a11y-contrast-utils, published on 4 Oct 2026.
Official description
[email protected] is advertised as a WCAG contrast utility but ships no contrast code — index.js exports an empty object. The package instead defines a Proxy stub exposing identifiers from Wix's internal Thunderbolt registry namespace (thunderboltRegistry, siteAssetsRegistry, editorRegistry, corvidRegistry, etc.), and its manifest points at static.parastorage.com/unpkg/css-a11y-contrast-utils, consistent with a dependency-confusion squat targeting a private Wix registry. On module load, thunderboltRegistry.js runs an IIFE that executes
hostname, id, and uname -r via child_process and exfiltrates the collected host, uid, kernel version, Node version, and pid by (a) issuing DNS lookups to subdomains of the hardcoded OAST collector davdpb8lhot13kgmnhp0863x9g83mpswq.oast.live and (b) HTTP GET to the hardcoded webhook https://webhook.site/0492a36c-4d7b-408a-865c-226db25987ba. The cover-story metadata plus internal-registry naming plus the on-load recon beacon make the entire purpose of the package a dependency-confusion payload against installers that resolve any of these registry names.What should I do about MAL-2026-17475?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.