Which versions of chalk-logger-prettier are malicious?

The following npm versions of chalk-logger-prettier are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.7, 1.0.8. Treat any of these as compromised.

How do I remediate chalk-logger-prettier if I installed it?

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

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

Yes — chalk-logger-prettier is associated with the GHSA-5qw7-4jj7-j7vf, RLMA-2026-05017, RLUA-2026-06149 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 chalk-logger-prettier across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chalk-logger-prettier (7 malicious versions).

Malicious package

chalk-logger-prettiernpm

Advisory published Jul 6, 2026Updated Sep 1, 2026

chalk-logger-prettier is a confirmed malicious npm package (MAL-2026-6809) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chalk-logger-prettier (npm)

MAL-2026-6809

Immediate action

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

npm uninstall chalk-logger-prettier

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.

Malicious versions

7 flagged

1.0.11.0.21.0.31.0.41.0.51.0.71.0.8

Indicators of compromise (SHA-256)

575cc2964157bd7bee9bc0c7b318af484ea57a2d89a904cd8fe8bf978809f06f

3fae678c7e944a397b7140017bb44621e21eccc654e0a275d40cdaf13742bdf1

074db9517b26f69650bb31a7f15b0a4f47e29942f83d534461aa3b97899f8220

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chalk-logger-prettier (7 malicious versions).
If you installed it — respond
Remove chalk-logger-prettier 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 chalk-logger-prettier 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. chalk-logger-prettier on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.7, 1.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5qw7-4jj7-j7vfRLMA-2026-05017RLUA-2026-06149

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks chalk-logger-prettier-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