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

pap-clientnpm

pap-client is a confirmed malicious npm package (MAL-2024-2834) that executes malicious code on install (malicious versions 0.9.9, 1.9.9, 9.9.9…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pap-client (npm)

MAL-2024-2834
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall pap-client

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
0.9.91.9.99.9.999.9.9

Indicators of compromise (SHA-256)

a34852380235302f453a6bda99bc96dd80621b0c4f25a701ff92374948710a39
f389d2d75f12fecbd4449f154638f14ddb3d7fc480f97703c160e1bae3ee565a
0aedde58db0099dc4a2595977fd29ec7682a84f55c56bee218753a6a340a6b2b
8f6d46042e4b781d62d50ea0127bc5dd72352e7141c2152cdaa7a7224d9c1e65

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pap-client (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pap-client across your stack and pipelines.

  2. If you installed it — respond

    Remove pap-client 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 pap-client 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.

  4. How O3 protects you

    O3 blocks pap-client 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. pap-client on npm has been identified as a malicious package (versions 0.9.9, 1.9.9, 9.9.9, 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-01548RLUA-2024-07065GHSA-jm4p-wwjp-rrhjRLUA-2026-01475

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks pap-client-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

pap-client (npm) malicious package — MAL-2024-2834 | O3 Security