How do I remediate piprce if I installed it?

piprce is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed piprce — how do I know if it already compromised me?

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

Yes — piprce is associated with the RLMA-2025-03663, GENERIC-standard-pypi-install-pentest, RLUA-2026-00595 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 piprce 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 piprce (43 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging piprce across your stack and pipelines.

Malicious package

piprcePyPI

Malicious code in piprce (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6566

Immediate action

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

pip uninstall piprce

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

43 flagged

0.0.10.0.20.0.30.0.40.0.50.0.60.0.70.0.80.0.90.1.00.1.10.1.20.1.30.1.40.1.50.1.60.1.70.1.80.1.8.50.1.8.60.1.8.70.1.8.80.1.8.90.1.90.2.10.2.20.2.30.2.40.2.50.2.60.2.70.2.80.2.8.10.2.8.20.2.8.30.2.8.40.2.8.50.2.8.60.2.8.70.2.8.80.2.90.3.00.3.1

Indicators of compromise (SHA-256)

e54943ea82bd9a9f07dcb01624d50f4dcf7a287ce025e79a382f4989f7913a01

994309f7bb5c72d472446d67c9de59003e8d7c3c447421d66b1153f4656a4f48

d83838279a89d5ade01981d993fcc70a555a562945268ccfc8f770a21910f55c

3a503af7229bedfc7e89e845d8cccdc5e77f3ec755e47ef9bcc022957390d50c

fc71afc121f45abcefb77ff96429b65253cd1b7a94377602cfaa9b05d03f54b6

48c89ddb060a1f78616d485d9728011dc9b11aa6529ae2f8fd6b44502905f74d

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for piprce (43 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging piprce across your stack and pipelines.
If you installed it — respond
piprce is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If piprce 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 piprce 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. piprce on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, and 35 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03663GENERIC-standard-pypi-install-pentestRLUA-2026-00595

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks piprce-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring