Which versions of pp-js-lib are malicious?

The following npm versions of pp-js-lib are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate pp-js-lib if I installed it?

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

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

Yes — pp-js-lib is associated with the GHSA-6hj5-4pqh-pfcv, RLMA-2026-01504 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 pp-js-lib 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 pp-js-lib (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pp-js-lib across your stack and pipelines.

Malicious package

pp-js-libnpm

Malicious code in pp-js-lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192561

Immediate action

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

npm uninstall pp-js-lib

What this malware does

The package pp-js-lib was found to contain malicious code.

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

1 flagged

999.0.0

Indicators of compromise (SHA-256)

ba1fcfff2f6e86511e78c7092763167dfd731beef4f008cc933bf1bb5b4255e1

21ef567b818a3642f6a51a1d26f23c897c1ecc73c6e431361ee1512d288ab455

856769d0723ff0e004de37e0cc7769cfba6efb1b25128026028cdda5be751f38

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

Campaign

GHSA-6hj5-4pqh-pfcvRLMA-2026-01504

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pp-js-lib-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