Which versions of prettier-logger are malicious?

The following npm versions of prettier-logger are flagged malicious: 0.1.4, 0.1.5, 0.1.6. Treat any of these as compromised.

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

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

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

Yes — prettier-logger is associated with the GHSA-6wq6-hvcw-xmcx, RLMA-2026-05230, RLUA-2026-06389 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 prettier-logger across my projects, lockfiles, and CI pipelines?

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

Malicious package

prettier-loggernpm

Advisory published Jul 6, 2026Updated Sep 1, 2026

prettier-logger is a confirmed malicious npm package (MAL-2026-6866) that executes malicious code on install (malicious versions 0.1.4, 0.1.5, 0.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in prettier-logger (npm)

MAL-2026-6866

Immediate action

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

npm uninstall prettier-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

3 flagged

0.1.40.1.50.1.6

Indicators of compromise (SHA-256)

0e5645051b8c021a473b5b5e8ffc5771c65265a02502beff5bef28932c4877cf

e4738dabd9c00ec73cf238cd88a4c00580a8dea2f5d24a9239c98d126e1b9570

84495d3894c032808efc2f5909a7d3500b534c30c961fe4fea27ad45086ee6bd

Detection & response playbook

Malicious package

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

Campaign

GHSA-6wq6-hvcw-xmcxRLMA-2026-05230RLUA-2026-06389

References

Credits

ReversingLabs · finder

Detect & block this

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