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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for testingpkgja (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testingpkgja across your stack and pipelines.

Malicious package

testingpkgjaPyPI

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for testingpkgja (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testingpkgja across your stack and pipelines.
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 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 testingpkgja 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. 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