Which versions of testpysecure are malicious?

The following PyPI versions of testpysecure are flagged malicious: 0.0.1, 1.1.1. Treat any of these as compromised.

How do I remediate testpysecure if I installed it?

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

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

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

Malicious package

testpysecurePyPI

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

MAL-2025-6600

Immediate action

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

pip uninstall testpysecure

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

0.0.11.1.1

Indicators of compromise (SHA-256)

01edca3be6a751c4a92f708396cad116b55d70729906a58d2f03cc68f0a2ff81

34a5bbbfa0f99425594e9d606d7d713034f791f6722763c44072ec3dda71bbb3

a202500c9717ad118db7ef8eb8d4c1de85c1afdbb442748e18010d4cf6222d5b

d9f2535f5138665fbf210c8ebe9b9a95fdbeacf2a761220bf82649d9520a438e

62e7ab11b868365e9429195360ee34bccdd6d35f754f92a73dc1753bb6225a3f

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

Campaign

RLMA-2025-03699GENERIC-standard-pypi-install-pentestRLUA-2026-00812

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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