Which versions of pino-zod are malicious?

The following npm versions of pino-zod are flagged malicious: 1.0.121, 1.0.122. Treat any of these as compromised.

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

pino-zod is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed pino-zod — how do I know if it already compromised me?

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

Yes — pino-zod is associated with the GHSA-j7hj-qc4f-x92f, IN-MAL-2026-009428, IN-MAL-2026-009440 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-zod 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-zod (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pino-zod across your stack and pipelines.

Malicious package

pino-zodnpm

pino-zod is a confirmed malicious npm package (MAL-2026-6505) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.121, 1.0.122). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pino-zod (npm)

MAL-2026-6505

Immediate action

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

npm uninstall pino-zod

What this malware does

Package advertises itself as a pino+zod logging helper but ships content that does not match that purpose: a dist/discordRelayUpload.js module containing POST/upload code paths and base64 buffer handling, a dist/relayServer.js module, a dist/secretScan/ tree (agentStartupAudit.js, contentScanner.js) that performs fetches against huggingface.co, a dist/hfCredentials.js with base64 decoding, a dist/deploymentDefaults.js with multiple base64 buffers, and a scripts/postinstall-agent.mjs containing GET/ping/id patterns. The presence of a postinstall-agent.mjs under scripts/ is concerning as a possible install-time agent, and the shipped relay/upload/secret-scan modules suggest behavior far outside the declared logging-library scope. However, without traced execution context confirming whether postinstall-agent.mjs is actually invoked by a lifecycle hook, where the base64 blobs decode to, and whether the Discord/HuggingFace endpoints carry installer data outward, the intent cannot be conclusively classified. Routing to human review for inspection of package.json lifecycle hooks, the contents of deploymentDefaults.js base64 payloads, and the data flow into the Discord upload and HuggingFace fetch paths.

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

2 flagged

1.0.1211.0.122

Indicators of compromise (SHA-256)

d57b4e49a62a8ca174c6c14820e5b101d042e3aea94438df19f9b12286a7cf30

651be849896c870c1c75ee04f5456ab7100090b688832af0bc822eaea9290ad3

92ceffaf94fc190f70c18587857f2f0a674a9699512eec79f5cf738eefaa54ca

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pino-zod (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pino-zod across your stack and pipelines.
If you installed it — respond
pino-zod is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If pino-zod 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-zod 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-zod on npm has been identified as a malicious package (versions 1.0.121, 1.0.122 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j7hj-qc4f-x92fIN-MAL-2026-009428IN-MAL-2026-009440

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pino-zod-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database