Which versions of minimal-a11y-contrast-check are malicious?

The following npm versions of minimal-a11y-contrast-check are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate minimal-a11y-contrast-check if I installed it?

minimal-a11y-contrast-check is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed minimal-a11y-contrast-check — how do I know if it already compromised me?

If minimal-a11y-contrast-check was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is minimal-a11y-contrast-check part of a known attack campaign?

Yes — minimal-a11y-contrast-check is associated with the IN-MAL-2026-020964 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find minimal-a11y-contrast-check across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for minimal-a11y-contrast-check (version 1.0.0).

Malicious package

minimal-a11y-contrast-checknpm

Advisory published Oct 4, 2026Updated Oct 4, 2026

minimal-a11y-contrast-check is a confirmed malicious npm package (MAL-2026-17514) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in minimal-a11y-contrast-check (npm)

MAL-2026-17514

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall minimal-a11y-contrast-check

What this malware does

Despite being advertised as a WCAG contrast checker, the package executes a self-invoking function at module load that runs host reconnaissance commands (whoami, id, hostname, uname -a, ls -la /, pwd, cat /etc/os-release) and collects filtered environment variables, then exfiltrates the results via DNS subdomain requests to davdpb8lhot13kgmnhp0863x9g83mpswq.oast.live and HTTP GET parameters to webhook.site/0492a36c-4d7b-408a-865c-226db25987ba. The exfiltration fires on any import of the package. Additionally, the module exports factories named after Wix Thunderbolt internal registries (thunderboltRegistry, siteAssetsRegistry, editorRegistry, corvidRegistry) and ships a registry-manifest.min.json pointing at static.parastorage.com/unpkg/[email protected], impersonating internal Wix build infrastructure to be resolved via dependency confusion. A hardcoded 'internetbrands' tag embedded in the exfiltration payload indicates targeted reconnaissance.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d9a198e6fb2c5e31bc841ff12f210e630abe8629853faf4ea961a124a9be8a25

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for minimal-a11y-contrast-check (version 1.0.0).
If you installed it — respond
minimal-a11y-contrast-check is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If minimal-a11y-contrast-check was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. minimal-a11y-contrast-check on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020964

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks minimal-a11y-contrast-check-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database