Which versions of pino-testkit are malicious?

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

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

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

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

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

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

Malicious package

pino-testkitnpm

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

Malicious code in pino-testkit (npm)

MAL-2026-16484

Immediate action

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

npm uninstall pino-testkit

What this malware does

[email protected] impersonates the widely-used pino logger: package.json declares the name pino-testkit with pino's description, lists Matteo Collina as author and the real pino maintainers as contributors, and the README is a mechanical copy of pino's README with pino rewritten to pino-testkit. The shipped source is largely a copy of pino with an extra file lib/contract.js wired in. pino.js exports chain, whose body calls contract(), so require('pino-testkit')(...) reaches the added file at load/call time. lib/contract.js uses a deterministic Fisher-Yates-style shuffle plus character substitution (\x25, \x23\x30, \x23\x31) to reconstruct the string Function and pluck Function off a captured global (ype[OUN]), then builds a new function from a second decoded body and immediately invokes it (cMp(7746)). Before doing so it hoists require and module onto global, so the dynamically constructed code can pull arbitrary further modules. Obfuscation of an executable payload combined with dynamic Function-constructor execution and require/module hoisting in a package that presents itself as pino is the canonical typosquat-dropper shape, giving the publisher arbitrary code execution on any consumer that requires or uses this package.

Malicious versions

1 flagged

10.4.5

Indicators of compromise (SHA-256)

f2711bf14b5de8acc2d8a401de585d09de28c4dc674331f6578acbc9ea36c6e7

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

Campaign

IN-MAL-2026-020498

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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