Which versions of @ctrl/tinycolor are malicious?

The following npm versions of @ctrl/tinycolor are flagged malicious: 4.1.1, 4.1.2. Treat any of these as compromised.

How do I remediate @ctrl/tinycolor if I installed it?

@ctrl/tinycolor 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 @ctrl/tinycolor — how do I know if it already compromised me?

If @ctrl/tinycolor 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 @ctrl/tinycolor part of a known attack campaign?

Yes — @ctrl/tinycolor is associated with the GHSA-qjqf-7j6f-82c4 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 @ctrl/tinycolor 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 @ctrl/tinycolor (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ctrl/tinycolor across your stack and pipelines.

Part of a larger attack: @ctrl published 14 malicious packages. See the full campaign →

Malicious package

@ctrl/tinycolornpm

@ctrl/tinycolor is a confirmed malicious npm package (MAL-2025-47141) that steals credentials and exfiltrates sensitive data (malicious versions 4.1.1, 4.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ctrl/tinycolor (npm)

MAL-2025-47141

Immediate action

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

npm uninstall @ctrl/tinycolor

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.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

2 flagged

4.1.14.1.2

Indicators of compromise (SHA-256)

21271c2ac161a78b2e79e14edbfba306dd2aa53c17aae63f3b009ba9288e1ddb

126ed7dd5bad8a311974a480d7caaa05dfee3e07d3e97830a4b4f1ca1e472467

6821cba2d7f1911b9015ce0d8597a8e0d81e3bb6b506682f289df5afbb2265c2

324615ccd53bf9d62a05b554eeba4b5e9887f9c6c45b1169126c667d419c8211

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

Campaign

GHSA-qjqf-7j6f-82c4

References

Detect & block this

O3 blocks @ctrl/tinycolor-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