pino-testkit has no safe version.

HighAdvisory sweepnpm

At least one advisory flags pino-testkit on the npm registry as malicious in every release, so the releases other advisories named are not the whole story. There is no version to upgrade to: remove it outright. It is named in 2 incidents we track. pino-testkit was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

Check my package-lock.json What to do

At a glancenpm

None

Safe versionsRemove it, do not upgrade

No release of this package is known good. If it is in your tree, treat the machine as compromised, not just out of date.

Ecosystem: npm
Worst severity: High
Incidents: 2
First flagged: 24 Sept 2026
Last flagged: 10 Oct 2026
Type: Advisory sweep

Version data comes from the public advisories cited on each incident page.

Version data

No release is known good. Including the releases the advisories named below.

Check what you actually have installed with npm ls pino-testkit.

The source advisories flagged the package itself rather than particular releases. Treat any resolved version as malicious and remove the dependency; there is nothing to upgrade to.

pino-testkit@10.4.5

The incidents

The 2 incidents that flagged it

HighAdvisory sweep10 Oct 2026

GitHub Advisory malware sweep, 10 October 2026

GHSA 2026-10-10: ~48 fresh malware advisories across 10 clusters (46 npm, 1 pypi, 1 crates). Headline items: new s4yhii operator native-binary credential-stealer dep-confusion cluster (16 packages across @galicia-toolkit-nestjs* and @brick-v2 scopes, prebuilds/metrics.node ELF+PE forks+setsid and exfils cloud/CI tokens to oob.s4yhii.com/native); first-seen crates.io infostealer sharpnes targeting Telegram Desktop sessions + Chrome extension/wallet data via Telegram Bot API; and @tunstock/remact-dom@19.2.0 react-dom typosquat with confirmed install-time beacon to tele.metry.orgin.net.

Versions named here: *Read the incident →

HighAdvisory sweep24 Sept 2026

GitHub Advisory malware sweep, 24 September 2026

GHSA 2026-09-23 (late) + 2026-09-24: ~25 new npm advisories + 1 pip + 1 rubygems. Day 7 of the oob.algamil7x.xyz DNS-OOB operator adds @baanx/common, @baanx/domain, and @insiderintelligence/componentlibrary. vite-dev-launcher@2.9.4 is a mall4cloud-react-RAT sibling of yesterdays @vitemirrorte. internallib_v657/v463` reverse shell to a new RFC1918 subnet.

Versions named here: 10.4.5Read the incident →

What to do

Installed one of these? Start here.

Treat the machine as compromisedUpgrading is not enough. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

Rotate every credential that machine or CI job could reach, such as registry tokens, cloud keys, SSH keys and CI secrets, from a different machine.
Remove the dependency: no release is known good, so there is nothing to pin to. Reinstall from a clean lockfile.
Clear caches and private mirrors. Artifactory, Nexus, Verdaccio and devpi routinely keep serving a tarball after the public registry has pulled it.
Read the incident write-up. Recommended actions differ per incident, and some have specific indicators of compromise worth searching your logs for.

Same campaign

Other packages in the same incident

If pino-testkit is in your tree, these are worth checking too. They were published by the same campaign.

See the full incident →All flagged npm packages →

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name and do not infer additional ones. Think this is wrong or incomplete? Tell us.

Check your whole project

Check every dependency, not just this one.

It is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once. It runs in your browser and nothing is uploaded.

Check my package-lock.json All npm packages