Which versions of testingpkgja are malicious?

The following PyPI versions of testingpkgja are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate testingpkgja if I installed it?

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

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

Yes — testingpkgja is associated with the GENERIC-simple-tests, RLMA-2025-06596, RLUA-2026-00807 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 testingpkgja across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for testingpkgja (version 0.1.0).

Malicious package

testingpkgjaPyPI

Advisory published Nov 23, 2025Updated Mar 19, 2026

testingpkgja is a confirmed malicious PyPI package (MAL-2025-191894) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testingpkgja (PyPI)

MAL-2025-191894

Immediate action

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

pip uninstall testingpkgja

What this malware does

Package downloads and starts an external executable. The executable starts the Windows calculator application. Considering this and the package description, this is a test of potentially malicious behaviour.

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

0.1.0

Indicators of compromise (SHA-256)

fca3e86fc2c86900f0d6417b3ea497f3fae95579011b0e12b07722b87f1fe972

0bd692e8fc46a3f43477d1f095e7c6e2b9666d2d2c60655ac91efd2be07f5193

df29cb02799d2e544ca550e855c0357955523f16afe29890425d9199562984d5

986fd7d161bdf0c6c62fecda614fdca77ecb7dafb18e25deca1ddefe7426040f

Detection & response playbook

Malicious package

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

Campaign

GENERIC-simple-testsRLMA-2025-06596RLUA-2026-00807

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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