Which versions of pretty-pino-logger are malicious?

The following npm versions of pretty-pino-logger are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 2.0.1, 2.0.2. Treat any of these as compromised.

How do I remediate pretty-pino-logger if I installed it?

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

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

Yes — pretty-pino-logger is associated with the GHSA-9vrr-rpr8-7hfj, RLMA-2026-05231, RLUA-2026-06392 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 pretty-pino-logger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pretty-pino-logger (7 malicious versions).

Malicious package

pretty-pino-loggernpm

Advisory published Jul 6, 2026Updated Sep 1, 2026

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

Malicious code in pretty-pino-logger (npm)

MAL-2026-6867

Immediate action

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

npm uninstall pretty-pino-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

7 flagged

1.0.01.0.11.0.21.0.31.0.42.0.12.0.2

Indicators of compromise (SHA-256)

c8a3122c1ab14fbe9f5eb55c0b5ba1db0c7b8e47ecc4d935b758d6bf679821e2

7dfe0e30069a0dfe487c302f46874a230788856e37c6088d59396238c7f27c94

1bddd2bfb94f8efe62312fbbe87ce3df6f9647e212a1f36efb39e10c4c345035

Detection & response playbook

Malicious package

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

Campaign

GHSA-9vrr-rpr8-7hfjRLMA-2026-05231RLUA-2026-06392

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks pretty-pino-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