Which versions of zod-pino444 are malicious?

The following npm versions of zod-pino444 are flagged malicious: 1.0.128, 1.0.129. Treat any of these as compromised.

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

zod-pino444 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 zod-pino444 — how do I know if it already compromised me?

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

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

Malicious package

zod-pino444npm

Malicious code in zod-pino444 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6795

Immediate action

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

npm uninstall zod-pino444

What this malware does

The package name mimics the popular zod and pino libraries but its shipped code implements a credential-harvest and relay pipeline that fires on install. scripts/postinstall-agent.mjs runs as a postinstall lifecycle hook, performing host reconnaissance (ping/GET/id) before invoking the bundled agent modules under dist/. dist/discordRelayUpload.js POSTs collected data to Discord relay endpoints (with base64-encoded payload construction and network reconnaissance on lines 39, 227, 306, 321, 398). dist/secretScan/agentStartupAudit.js and dist/secretScan/contentScanner.js scan for secrets and exfiltrate them via fetch calls to https://huggingface.co endpoints (lines 490, 508, 563). dist/hfCredentials.js and dist/deploymentDefaults.js decode base64-embedded configuration/credentials at load time. The typosquat-style name, obfuscated base64 payloads across multiple modules, install-time execution, and hardcoded exfiltration destinations together match the active-attack fingerprint (credential collection + hardcoded C2 + install-time auto-execution). The safety filter withheld traced-code output for this package, consistent with operational malware content.

Malicious versions

2 flagged

1.0.1281.0.129

Indicators of compromise (SHA-256)

94d359a15f76e30c9a9140d2ca33e502c5ab39acf9a12dffa9cd865831bc919d

bcb90d28a4c4697db5173503735e9c4a9cbf9e9360265834b9b307bfcc3c6f3b

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

Campaign

IN-MAL-2026-007957IN-MAL-2026-007959

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zod-pino444-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