Which versions of peptest2 are malicious?

The following PyPI versions of peptest2 are flagged malicious: 1.2.2, 1.2.3. Treat any of these as compromised.

How do I remediate peptest2 if I installed it?

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

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

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

Malicious package

peptest2PyPI

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

MAL-2025-191813

Immediate action

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

pip uninstall peptest2

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

2 flagged

1.2.21.2.3

Indicators of compromise (SHA-256)

d8efde2f9d8f24878f597969201158e0ffbef22f240f8abe8cf14b0f1bbdb347

60249233a6c88847f2043da362196e4b2652bd7dddb8dbfe92cc3e7b2b2676a9

06f37f4da9e84ef37d43dfb4909ff9992c3a6f0e9bc8f2fe8fba3cc6f7a44b41

9f7f49eeeb3645a4d00478512c472ff90f5119d8f7a73756a814f948bf65612b

c9ee09ca1a226f8fc054119ff303adb9ce669a77a35b6d724c75bf78a3c6e648

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

Campaign

GENERIC-standard-pypi-install-pentestRLMA-2025-06579RLUA-2026-00587

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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