Which versions of testpurpleteaming are malicious?

The following PyPI versions of testpurpleteaming are flagged malicious: 1.26.10, 1.26.13, 1.26.14. Treat any of these as compromised.

How do I remediate testpurpleteaming if I installed it?

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

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

Yes — testpurpleteaming is associated with the GENERIC-standard-pypi-install-pentest 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 testpurpleteaming across my projects, lockfiles, and CI pipelines?

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

Malicious package

testpurpleteamingPyPI

Advisory published Nov 6, 2025Updated Dec 31, 2025

testpurpleteaming is a confirmed malicious PyPI package (MAL-2025-191895) that steals credentials and exfiltrates sensitive data (malicious versions 1.26.10, 1.26.13, 1.26.14). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testpurpleteaming (PyPI)

MAL-2025-191895

Immediate action

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

pip uninstall testpurpleteaming

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.26.101.26.131.26.14

Indicators of compromise (SHA-256)

0fe53e58a334a93d294bcc842d0e8dffeb641d4d3e47697f14d5efb68f57646e

e4cc49d59c07354a2817163d4e569b1f6d2e6cf17c5c7fb0135bc5feebdfea4e

5040fc8eba3b27b847e26a52320a16c5ba1cda610bb8fce4bec8df244c20e3a6

Detection & response playbook

Credential / info stealer

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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