Which versions of color-utils-dee0 are malicious?

The following npm versions of color-utils-dee0 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate color-utils-dee0 if I installed it?

color-utils-dee0 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 color-utils-dee0 — how do I know if it already compromised me?

If color-utils-dee0 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is color-utils-dee0 part of a known attack campaign?

Yes — color-utils-dee0 is associated with the IN-MAL-2026-006966, GHSA-f8p9-v2xw-79xc 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 color-utils-dee0 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for color-utils-dee0 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging color-utils-dee0 across your stack and pipelines.

Malicious package

color-utils-dee0npm

color-utils-dee0 is a confirmed malicious npm package (MAL-2026-6089) 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 color-utils-dee0 (npm)

MAL-2026-6089

Immediate action

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

npm uninstall color-utils-dee0

What this malware does

package.json declares a postinstall hook ("postinstall": "node run.js") that automatically runs run.js on npm install. run.js imports child_process, os, http, and https, reads host identifiers via os.hostname() and os.platform(), and performs outbound HTTP/HTTPS GET and POST calls (run.js lines 48, 62, 63, 265). The combination of automatic install-time execution, host fingerprinting, child_process availability, and outbound network POSTs of host data is the canonical install-time exfiltration / dropper shape. The package name (a short, randomly-suffixed color-utils-dee0) and v1.0.0-only release are consistent with a disposable squat/lure rather than a legitimate utility. Installing this package will run attacker-chosen code with the installer's privileges and leak host information to an external endpoint.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a6d19450c3691562b0a498e497c1c6abde10e822eac4735cffc6f6513a7b471f

e502d4f31039aebceac601820264b22b2ea3182c51b5a906d24fde90e4a62fba

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for color-utils-dee0 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging color-utils-dee0 across your stack and pipelines.
If you installed it — respond
color-utils-dee0 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 color-utils-dee0 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks color-utils-dee0 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. color-utils-dee0 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-006966GHSA-f8p9-v2xw-79xc

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks color-utils-dee0-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