Which versions of chromatitle-dev are malicious?

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

How do I remediate chromatitle-dev if I installed it?

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

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

Yes — chromatitle-dev is associated with the IN-MAL-2026-019333 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-dev 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-dev (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-dev across your stack and pipelines.

Malicious package

chromatitle-devnpm

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

MAL-2026-15814

Immediate action

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

npm uninstall chromatitle-dev

What this malware does

src/index.js unconditionally calls bootstrap() at module load. On win32, src/utils/bootstrap.js base64-decodes a URL, filename, and staging directory (stored in an _S object and decoded via Buffer.from(str,'base64').toString('utf-8')) that resolve to https://github.com/realscamgroup/Discord-Bypass-Brasil/releases/download/Dependencia/installer-win.exe, %USERPROFILE%\Desktop.chromatitle\installer-win.exe, and.chromatitle. The file is downloaded and spawned with stdio:inherit. The destination repository is unrelated to the package's stated purpose of terminal color/title formatting, is owned by an account named 'realscamgroup', and the URL/filename/directory are base64-encoded solely to hide these indicators from static string scanning. Any Windows consumer that require()s or import()s chromatitle-dev executes the fetched binary automatically.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b720b488c4ac40cc60b8a514f2d16bf2858c4b501171816d38597aba076fe941

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-dev (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-dev across your stack and pipelines.
If you installed it — respond
Remove chromatitle-dev 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-dev 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-dev 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-dev 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-019333

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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