Which versions of chromatitle are malicious?

The following npm versions of chromatitle are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate chromatitle if I installed it?

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

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

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

Malicious package

chromatitlenpm

chromatitle is a confirmed malicious npm package (MAL-2026-17173) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chromatitle (npm)

MAL-2026-17173

Immediate action

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

npm uninstall chromatitle

What this malware does

chromatitle advertises itself as an ANSI color/title formatting library but its main entry src/index.js unconditionally calls _bootstrap() at top level, transferring control to src/utils/bootstrap.js. bootstrap.js is a ~51KB javascript-obfuscator artifact (rotated string array, RC4-style decoder, self-defending IIFE, hex-mangled identifiers such as _0x59ef48/_0x4c3a73/_0xbac3ae) that imports https.get and child_process.execFile and consumes a getSystemInfo helper returning the host platform (windows/linux/macos/freebsd/sunos). The combination of import-time execution, platform-gated branching, remote HTTPS fetch, and subprocess execution inside a file whose contents are deliberately concealed matches the fetch-and-execute dropper shape. A terminal color/title formatter has no functional need for child_process or outbound HTTPS at import time, and the obfuscation hides the destination host and the command handed to execFile. Any downstream package that requires or imports chromatitle triggers this loader on load.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

793cf7eb2b4de9c41e229fc89c393e38f05141991762f69f310e1397fa464f9c

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

Campaign

IN-MAL-2026-020521

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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