Which versions of peptest are malicious?

The following PyPI versions of peptest are flagged malicious: 1.0.0, 1.2.0, 1.2.1. Treat any of these as compromised.

How do I remediate peptest if I installed it?

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

If peptest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is peptest part of a known attack campaign?

Yes — peptest is associated with the GENERIC-standard-pypi-install-pentest, RLMA-2025-06578, RLUA-2026-00586 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 peptest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for peptest (3 malicious versions).

Malicious package

peptestPyPI

Advisory published Nov 20, 2025Updated Mar 19, 2026

peptest is a confirmed malicious PyPI package (MAL-2025-191812) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.2.0, 1.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in peptest (PyPI)

MAL-2025-191812

Immediate action

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

pip uninstall peptest

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

3 flagged

1.0.01.2.01.2.1

Indicators of compromise (SHA-256)

9ae640cbfc50fbe6bf010721d445902c56577b9a1a5dd44e796e71efc2d7bedd

1230d903d5782f1a6d2d779ada368260f2c32d9e4f74bfd3ddd8f4df9c570572

e6a6a5147a29c39806d36d59d54fb3a86bbdedcf834d03536c6c2ea68f33983c

960d8de4f38a7c0ce09a2e750d83073f7455207ce8590c9526cccadab0840f4c

8fc9558d1eecec30d555da224cbd6f2bbaab9165faa3ec95e88e7a6ad4c67357

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for peptest (3 malicious versions).
If you installed it — respond
peptest 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 peptest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. peptest on PyPI has been identified as a malicious package (versions 1.0.0, 1.2.0, 1.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestRLMA-2025-06578RLUA-2026-00586

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database