Which versions of colorpicker-ui are malicious?

The following npm versions of colorpicker-ui are flagged malicious: 1.2.4, 1.2.5. Treat any of these as compromised.

How do I remediate colorpicker-ui if I installed it?

colorpicker-ui 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 colorpicker-ui — how do I know if it already compromised me?

If colorpicker-ui 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 colorpicker-ui part of a known attack campaign?

Yes — colorpicker-ui is associated with the IN-MAL-2026-007532, IN-MAL-2026-007533 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 colorpicker-ui 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 colorpicker-ui (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging colorpicker-ui across your stack and pipelines.

Malicious package

colorpicker-uinpm

colorpicker-ui is a confirmed malicious npm package (MAL-2026-6473) that steals credentials and exfiltrates sensitive data (malicious versions 1.2.4, 1.2.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in colorpicker-ui (npm)

MAL-2026-6473

Immediate action

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

npm uninstall colorpicker-ui

What this malware does

Package presents itself as a minimal React color-picker but ships a postinstall hook ("postinstall": "node setup.js") that performs targeted credential theft and code-injection staging on npm install. setup.js reads classic installer secrets — /var/run/secrets/kubernetes.io/serviceaccount/token (Kubernetes service-account token granting cluster API access), the AWS Instance Metadata Service at http://169.254.169.254/latest/meta-data/ (cloud instance credentials), /etc/passwd, /etc/resolv.conf, /etc/hosts, the full process.env, and runs id / uname -a plus a recursive listing of /app. The harvested data is wrapped as export default "..."; and written to multiple attacker-chosen paths including /app/sandbox-data/workspace/frontend/_rce.ts, ../frontend/_rce.ts, and /tmp/rce.json. The _rce.ts filename and the targeting of adjacent frontend workspace directories are designed to land the file inside AI coding-agent / sandbox workspaces that auto-import files from the workspace tree, converting the postinstall into arbitrary code execution in the next agent run while also exfiltrating the secrets to whatever process consumes the file. The advertised color-picker API in index.js (ColorPicker, hexToHsl, hslToHex) is functional but exists solely as cover; a color-picker library has no need to read kubernetes tokens, IMDS, or /etc/passwd at install. The log message 'generating default theme cache' printed by setup.js is deliberately misleading.

Malicious versions

2 flagged

1.2.41.2.5

Indicators of compromise (SHA-256)

226e4e81049c5688a16a198fb9a90ab3d11d371b621e367da4590632f4e5e140

f49dd7e4550f9b9e0ffa3e412a40882e9d7a45eacdc3221e590b41e3e7a15e13

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 colorpicker-ui (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging colorpicker-ui across your stack and pipelines.
If you installed it — respond
colorpicker-ui 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 colorpicker-ui 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 colorpicker-ui 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. colorpicker-ui on npm has been identified as a malicious package (versions 1.2.4, 1.2.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007532IN-MAL-2026-007533

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks colorpicker-ui-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