Which versions of test-py-conn are malicious?

The following PyPI versions of test-py-conn are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate test-py-conn if I installed it?

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

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

Yes — test-py-conn is associated with the 2026-05-test-py-conn 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-py-conn across my projects, lockfiles, and CI pipelines?

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

Malicious package

test-py-connPyPI

Advisory published May 6, 2026Updated May 6, 2026

test-py-conn is a confirmed malicious PyPI package (MAL-2026-3356) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-py-conn (PyPI)

MAL-2026-3356

Immediate action

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

pip uninstall test-py-conn

What this malware does

The code automatically starts a worker designed to survive the exit of the main process. The worker load code from a PYC file which then connects to pre-defined C2 server and awaits commands to execute.

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

Campaign: 2026-05-test-py-conn

Reasons (based on the campaign):

The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
rat

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

7e39e3b24f15db8e5eff412ba6cb217986b6f80b6923712abd1efee4cf79a7ed

Detection & response playbook

Credential / info stealer

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

Campaign

2026-05-test-py-conn

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks test-py-conn-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