Which versions of pino-deploy are malicious?

The following npm versions of pino-deploy are flagged malicious: 0.0.1, 0.0.2, 1.0.0. Treat any of these as compromised.

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

Remove pino-deploy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — pino-deploy is associated with the RLMA-2024-01591, RLUA-2024-07094, GHSA-9hw3-p3rx-59cw 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-deploy 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-deploy (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pino-deploy across your stack and pipelines.

Malicious package

pino-deploynpm

pino-deploy is a confirmed malicious npm package (MAL-2024-2871) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pino-deploy (npm)

MAL-2024-2871

Immediate action

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

npm uninstall pino-deploy

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

0.0.10.0.21.0.0

Indicators of compromise (SHA-256)

49feaac8f88fbaca6d0e969491cfd47ae32ef391093672eb16e2deb0d8b19945

aab96bad072f091d9b86b5b60b7efa2c3ee894215ac199950dcd1b757eece5e6

22aa2a34d1bc80289998fa9f16a0a8731eacac719b3068a84c1e3b93dd880f1c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pino-deploy (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pino-deploy across your stack and pipelines.
If you installed it — respond
Remove pino-deploy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If pino-deploy 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-deploy 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-deploy on npm has been identified as a malicious package (versions 0.0.1, 0.0.2, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-01591RLUA-2024-07094GHSA-9hw3-p3rx-59cw

References

Credits

ReversingLabs · finder

Detect & block this

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