Which versions of terminalcolor256 are malicious?

The following npm versions of terminalcolor256 are flagged malicious: 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, and 1 more. Treat any of these as compromised.

How do I remediate terminalcolor256 if I installed it?

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

If terminalcolor256 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is terminalcolor256 part of a known attack campaign?

Yes — terminalcolor256 is associated with the RLMA-2025-04704, RLUA-2026-02047 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 terminalcolor256 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for terminalcolor256 (21 malicious versions).

Malicious package

terminalcolor256npm

Advisory published Aug 14, 2025Updated Apr 16, 2026

terminalcolor256 is a confirmed malicious npm package (MAL-2025-34723) that executes malicious code on install (malicious versions 2.0.2, 2.0.3, 2.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in terminalcolor256 (npm)

MAL-2025-34723

Immediate action

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

npm uninstall terminalcolor256

What this malware does

The package terminalcolor256 was found to contain malicious code.

Malicious versions

21 flagged

2.0.22.0.32.0.42.0.52.0.62.0.72.0.82.0.92.1.02.1.12.1.22.1.32.1.42.1.52.2.02.2.12.2.22.2.32.2.42.2.52.2.6

Indicators of compromise (SHA-256)

76e0fa16ca09b1bd9069c4ded0fdc6929bd2b8cd36f99d6f51fa80b73b9d324e

b48dcef1e919f085bb2f16cc1d4ea4f9c4e490a7291eb403b3cf3ac796ef1aa5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for terminalcolor256 (21 malicious versions).
If you installed it — respond
Remove terminalcolor256 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 terminalcolor256 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. terminalcolor256 on npm has been identified as a malicious package (versions 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, and 13 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04704RLUA-2026-02047

References

reversinglabs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks terminalcolor256-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