Which versions of pitest115 are malicious?

The following PyPI versions of pitest115 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate pitest115 if I installed it?

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

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

Yes — pitest115 is associated with the GENERIC-simple-tests 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 pitest115 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pitest115 (version 1.0.0).

Malicious package

pitest115PyPI

Advisory published Aug 23, 2024Updated Dec 12, 2025

pitest115 is a confirmed malicious PyPI package (MAL-2024-12325) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pitest115 (PyPI)

MAL-2024-12325

Immediate action

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

pip uninstall pitest115

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

fdb5ac225762e61ca928ab4bee0346603c887b15b4a05add961d66b2ff87ead2

eafda224bcd5572ef89818a64323563992432421a36cdec585dee3dc0a04469c

43e61f49065a6e43b3f02a21f0952e3c266bd03c014d2cd0907a391144405128

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pitest115 (version 1.0.0).
If you installed it — respond
Remove pitest115 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 pitest115 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. pitest115 on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-tests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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