# MAL-2026-6089: Malicious code in color-utils-dee0 (npm)


- **Type:** Malicious package
- **Package:** `color-utils-dee0` (npm)
- **Published:** 18 Jun 2026
- **Also known as:** GHSA-f8p9-v2xw-79xc

## What is MAL-2026-6089?

MAL-2026-6089 is a malicious package in color-utils-dee0, published on 18 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-6089?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6089 is a malicious package: color-utils-dee0 (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-6089/ (Markdown: https://insights.sbomify.com/MAL-2026-6089/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6089

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6089/
Summaries are generated and may contain mistakes; the official description above is the record.