Which versions of eth-pino are malicious?

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

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

eth-pino is a typosquat — you almost certainly intended a legitimately-named package. Remove eth-pino, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

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

Malicious package

eth-pinonpm

eth-pino is a confirmed malicious npm package (MAL-2026-15554) that typosquats a legitimate package to trick installs (malicious version 2.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eth-pino (npm)

MAL-2026-15554

Immediate action

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

npm uninstall eth-pino

What this malware does

On require, lib/initializeCaller.js runs a top-level async IIFE that decodes a base64-obfuscated URL to https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df and POSTs a shallow copy of process.env to that endpoint with an x-secret-header header. The HTTP response body is then passed to new Function('require', response.data) and invoked with the real require, granting the remote operator arbitrary code execution in the installer's Node.js process. The destination URL is stored as a base64 literal to evade static URL scanners. The package name and file layout mimic the legitimate pino logger while the exported middleware is a no-op, consistent with typosquat delivery.

Malicious versions

1 flagged

2.0.3

Indicators of compromise (SHA-256)

81e08c035ca41519f1d57d389027befac80a8ee8405612825b633967db5fb8c1

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eth-pino (version 2.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eth-pino across your stack and pipelines.
If you installed it — respond
eth-pino is a typosquat — you almost certainly intended a legitimately-named package. Remove eth-pino, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If eth-pino 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 eth-pino 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. eth-pino on npm has been identified as a malicious package (version 2.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019139

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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