Which versions of test-packages1 are malicious?

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

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

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

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

Yes — test-packages1 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-packages1 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 test-packages1 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-packages1 across your stack and pipelines.

Malicious package

test-packages1PyPI

Malicious code in test-packages1 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12359

Immediate action

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

pip uninstall test-packages1

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)

c60c102f9f6ceedd506c000b76c2d9bc8cb9de87dae7007d3888169a1c6a0d98

5c5608702af52a2ca19f0b384036f76248848f4b4ddbe582631d85b3f5e77dca

066ac6f5ce3ec3b9e427561d028af8136188144ec83d09c97667128e25afb9ea

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 test-packages1 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-packages1 across your stack and pipelines.
If you installed it — respond
test-packages1 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-packages1 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 test-packages1 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. test-packages1 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-packages1-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