NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

chromatitle-jsnpm

Advisory published Updated

chromatitle-js is a confirmed malicious npm package (MAL-2026-17174) 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-js (npm)

MAL-2026-17174
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall chromatitle-js

What this malware does

src/index.js unconditionally invokes _bootstrap() from src/utils/bootstrap.js at module load time. bootstrap.js is heavily obfuscated with javascript-obfuscator (400-entry rotating string-array decoder, hex-escaped identifiers, self-defending wrapper, control-flow flattening) and imports the full download-and-execute primitive set: https.get/http.get, fs.createWriteStream, fs.mkdirSync, fs.chmodSync, fs.unlinkSync, os.tmpdir, and child_process.execFile/spawn. The destination URL, dropped filename, and executed argv are reconstructed at runtime from the obfuscated string array, so the network target and payload are concealed from static inspection. package.json declares javascript-obfuscator as a devDependency and defines an obfuscate build script, confirming the concealment is deliberate. The advertised purpose of the package is terminal string coloring / title setting, which does not require fetching or executing a binary at import time. Any consumer that imports chromatitle-js triggers the fetch-and-execute chain on the installer's machine.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

eff7b9f53e0aed7a8a1c48ae92851ea0ed67b86566d208c78329ecb1b8a73173

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for chromatitle-js (version 1.0.0).

  2. If you installed it — respond

    Remove chromatitle-js 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.

  3. Did it already run?

    If chromatitle-js 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. chromatitle-js 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-020522

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

chromatitle-js (npm) malicious package — MAL-2026-17174 | O3 Security