Which versions of colortoolsv2 are malicious?

The following npm versions of colortoolsv2 are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate colortoolsv2 if I installed it?

Remove colortoolsv2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed colortoolsv2 — how do I know if it already compromised me?

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

Yes — colortoolsv2 is associated with the GHSA-748f-36r4-4gj6, RLMA-2025-03801, RLUA-2025-05705 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 colortoolsv2 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 colortoolsv2 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging colortoolsv2 across your stack and pipelines.

Malicious package

colortoolsv2npm

colortoolsv2 is a confirmed malicious npm package (MAL-2025-5842) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in colortoolsv2 (npm)

MAL-2025-5842

Immediate action

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

npm uninstall colortoolsv2

What this malware does

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

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

35da23355879f7db0f986508b2d2540d9d12942545cab651d9b50a9312d074ca

5dcc07f13397a2a43a1bfea37a9c1017223734dd4b5e63d539519e02ecdfd0f6

a1dd95ba4f97f5e83c855df784d538837526be2499807a9d68c98c84e7667e0b

4b37737f8a9e90ec8551f4639c2ec2d8acbab26c470397a55a478895e97d4449

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for colortoolsv2 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging colortoolsv2 across your stack and pipelines.
If you installed it — respond
Remove colortoolsv2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If colortoolsv2 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 colortoolsv2 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. colortoolsv2 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-748f-36r4-4gj6RLMA-2025-03801RLUA-2025-05705

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks colortoolsv2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database