Which versions of @voiceflow/pino are malicious?

The following npm versions of @voiceflow/pino are flagged malicious: 6.11.3, 6.11.4. Treat any of these as compromised.

How do I remediate @voiceflow/pino if I installed it?

@voiceflow/pino 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 @voiceflow/pino — how do I know if it already compromised me?

If @voiceflow/pino was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @voiceflow/pino across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @voiceflow/pino (2 malicious versions).

Part of a larger attack: @voiceflow published 57 malicious packages. See the full campaign →

Malicious package

@voiceflow/pinonpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@voiceflow/pino is a confirmed malicious npm package (MAL-2025-191364) that steals credentials and exfiltrates sensitive data (malicious versions 6.11.3, 6.11.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @voiceflow/pino (npm)

MAL-2025-191364

Immediate action

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

npm uninstall @voiceflow/pino

What this malware does

The package @voiceflow/pino was found to contain malicious code.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

6.11.36.11.4

Indicators of compromise (SHA-256)

9400a5fb12a8bd43aef8c4951be3c72ff0843e530c44f403d2d03bf881132100

980243b18346b941c1cb5c2390751258de1c019b02526dbbd7ad2b2e41069656

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @voiceflow/pino (2 malicious versions).
If you installed it — respond
@voiceflow/pino 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 @voiceflow/pino was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @voiceflow/pino on npm has been identified as a malicious package (versions 6.11.3, 6.11.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @voiceflow/pino-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