Which versions of test-packages2 are malicious?

The following PyPI versions of test-packages2 are flagged malicious: 0.1, 0.1.1. Treat any of these as compromised.

How do I remediate test-packages2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for test-packages2 (2 malicious versions).

Malicious package

test-packages2PyPI

Advisory published Sep 6, 2024Updated Dec 12, 2025

test-packages2 is a confirmed malicious PyPI package (MAL-2024-12360) that steals credentials and exfiltrates sensitive data (malicious versions 0.1, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-packages2 (PyPI)

MAL-2024-12360

Immediate action

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

pip uninstall test-packages2

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

2 flagged

0.10.1.1

Indicators of compromise (SHA-256)

551eef4d9ca854d6a111521634d2a180b1df038a09207671a1d7bd6f29630c01

4336b840413f8b1d796d06001cd5fb057d2e92276771ec70122834253e5e41f3

8c505f9143086d255a539c36bb2c1fdcd0c95dcca19415d0cc3e2d730179135b

Detection & response playbook

Credential / info stealer

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

Campaign

GENERIC-questionable-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks test-packages2-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