Which versions of pampipes are malicious?

The following npm versions of pampipes are flagged malicious: 1.1.9, 1.2.0, 1.2.9, 1.3.0. Treat any of these as compromised.

How do I remediate pampipes if I installed it?

Remove pampipes 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 pampipes — how do I know if it already compromised me?

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

Yes — pampipes is associated with the GHSA-j43p-473c-2jjx, RLMA-2026-05202, RLUA-2026-05589 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 pampipes 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 pampipes (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pampipes across your stack and pipelines.

Malicious package

pampipesnpm

pampipes is a confirmed malicious npm package (MAL-2026-5872) that executes malicious code on install (malicious versions 1.1.9, 1.2.0, 1.2.9…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pampipes (npm)

MAL-2026-5872

Immediate action

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

npm uninstall pampipes

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

4 flagged

1.1.91.2.01.2.91.3.0

Indicators of compromise (SHA-256)

660a84b18bd4e15af0f490d3f4bfde871b12e7912493f23d5ae7a3db10a82565

9c1b2c58dbee411e19253f2b812bf4b803b456e1ccd1880fe8f15dc6e82b80e0

0ab1e27ac5e56f4b97496300942a4ecd2501e9a6bcb0d2ad8d3138258b27def3

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 pampipes (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pampipes across your stack and pipelines.
If you installed it — respond
Remove pampipes 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 pampipes 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 pampipes 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. pampipes on npm has been identified as a malicious package (versions 1.1.9, 1.2.0, 1.2.9, 1.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j43p-473c-2jjxRLMA-2026-05202RLUA-2026-05589

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks pampipes-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