Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

pino-deploynpm

Advisory published Updated

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
8ea6859d7fff9147bf55fbcacf1be84bf585e3f68a1ef69ba6c750e4f04dc418

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for pino-deploy (3 malicious versions).

  2. 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.

  3. Did it already run?

    If pino-deploy 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. 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-59cwRLUA-2026-10775

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.

Explore

pino-deploy (npm) malicious package — MAL-2024-2871 | O3 Security