Which versions of pretty-ts-logger are malicious?

Every published version of pretty-ts-logger on npm is considered malicious. Remove the package entirely.

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

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

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

Yes — pretty-ts-logger is associated with the GHSA-7qv7-jx74-qhx9 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-ts-logger 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 pretty-ts-logger (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pretty-ts-logger across your stack and pipelines.

Malicious package

pretty-ts-loggernpm

Malicious code in pretty-ts-logger (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1965

Immediate action

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

npm uninstall pretty-ts-logger

What this malware does

The package pretty-ts-logger was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

0c811c327f0147313f0f5362e62e94d0aadf15ac53937bb3e88b133748db9c67

3252c2860c3dca66dbc03f90407ce4f37b310c8e4f6bfc6485625b1b7d926cd2

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 pretty-ts-logger (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pretty-ts-logger across your stack and pipelines.
If you installed it — respond
Remove pretty-ts-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-ts-logger 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 pretty-ts-logger 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. pretty-ts-logger on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7qv7-jx74-qhx9

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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