Which versions of pino-logger-utils are malicious?

The following npm versions of pino-logger-utils are flagged malicious: 1.0.0. Treat any of these as compromised.

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

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

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

Yes — pino-logger-utils is associated with the GHSA-9vc6-vqg8-v9x5, RLMA-2026-01488, RLUA-2026-02022 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 pino-logger-utils 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 pino-logger-utils (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pino-logger-utils across your stack and pipelines.

Malicious package

pino-logger-utilsnpm

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

MAL-2026-1493

Immediate action

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

npm uninstall pino-logger-utils

What this malware does

The package pino-logger-utils 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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f10cc97f411b17fedd56c3302dc91bc064f9efd2c238f00066cfcd4a51c26d51

06ca915c66b82f4a2d13779dab17f5ea2e8c01ac2f59773989c12a39c5ec5e08

d5c908d1d5a0d2a6a517ef1aa6e7ab5b7ddc8644dc39730c2629f0226a69121a

4db1c3eaae11cb7405350b65abe9c6584ecdf0f76583cd6faabb6f86b8cab1b5

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

Campaign

GHSA-9vc6-vqg8-v9x5RLMA-2026-01488RLUA-2026-02022

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pino-logger-utils-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