Which versions of pmcrypto are malicious?

The following npm versions of pmcrypto are flagged malicious: 0.1.0, 99.99.99. Treat any of these as compromised.

How do I remediate pmcrypto if I installed it?

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

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

Yes — pmcrypto is associated with the RLMA-2025-03976, GHSA-4rrv-2r5h-p7x7, RLUA-2025-05918 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 pmcrypto 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 pmcrypto (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pmcrypto across your stack and pipelines.

Malicious package

pmcryptonpm

pmcrypto is a confirmed malicious npm package (MAL-2025-6645) that executes malicious code on install (malicious versions 0.1.0, 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pmcrypto (npm)

MAL-2025-6645

Immediate action

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

npm uninstall pmcrypto

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

2 flagged

0.1.099.99.99

Indicators of compromise (SHA-256)

e573d4c8f28ac017a409833fdd1352bab30629841c9deaf3e133a552b9c7ac3d

57ffdc79307f9124b4b16f188f8256bf619280bcebec697f5817c7d6c5f1e999

a70d8f6e75a22c59c2a0d9bcb4cf219974fff4da61393a5e05a62275d8afce87

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

Campaign

RLMA-2025-03976GHSA-4rrv-2r5h-p7x7RLUA-2025-05918

References

Credits

ReversingLabs · finder

Detect & block this

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