Which versions of pino-std are malicious?

The following npm versions of pino-std are flagged malicious: 7.2.0. Treat any of these as compromised.

How do I remediate pino-std if I installed it?

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

If pino-std 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.

How do I find pino-std across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pino-std (version 7.2.0).

Malicious package

pino-stdnpm

Advisory published Oct 26, 2026Updated Nov 5, 2026

pino-std is a confirmed malicious npm package (MAL-2026-18692) that executes malicious code on install (malicious version 7.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pino-std (npm)

MAL-2026-18692

Immediate action

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

npm uninstall pino-std

What this malware does

pino-std ships lib/contract.js, byte-identical to the pino-testkit payload: a copy of the pino logger with an extra obfuscated module that decodes and evaluates code at load. It is a new name for the pino-testkit (MAL-2026-16484) campaign; the file hashes below match that record's evidence. The package presents itself as an ordinary utility, so the code runs on import or install without the user knowing.

Malicious versions

1 flagged

7.2.0

Detection & response playbook

Malicious package

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

References

Credits

CyberXYZ · finder

Detect & block this

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