Which versions of awesome-cli-logger are malicious?

The following npm versions of awesome-cli-logger are flagged malicious: 1.0.0, 1.2.0. Treat any of these as compromised.

How do I remediate awesome-cli-logger if I installed it?

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

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

Yes — awesome-cli-logger is associated with the GHSA-4j38-wfq5-cfxw, RLMA-2026-04951, RLUA-2026-06076 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 awesome-cli-logger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for awesome-cli-logger (2 malicious versions).

Malicious package

awesome-cli-loggernpm

Advisory published Jul 6, 2026Updated Sep 1, 2026

awesome-cli-logger is a confirmed malicious npm package (MAL-2026-6799) that executes malicious code on install (malicious versions 1.0.0, 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in awesome-cli-logger (npm)

MAL-2026-6799

Immediate action

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

npm uninstall awesome-cli-logger

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

2 flagged

1.0.01.2.0

Indicators of compromise (SHA-256)

8126f65c2eaf406ae6c6510e03e8bbef8f243974be621b7e38a0c52d9e521a18

8c605fd27fae32e046d8c24403bcc09eaa11d24eab3b47882f86902f7841f071

b036021cad9e4780a327d431008ec33230aed07a0ce1eebe01cac83b9c43af84

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for awesome-cli-logger (2 malicious versions).
If you installed it — respond
Remove awesome-cli-logger 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 awesome-cli-logger 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. awesome-cli-logger on npm has been identified as a malicious package (versions 1.0.0, 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4j38-wfq5-cfxwRLMA-2026-04951RLUA-2026-06076

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks awesome-cli-logger-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