Which versions of testingpy are malicious?

The following PyPI versions of testingpy are flagged malicious: 0.1.3. Treat any of these as compromised.

How do I remediate testingpy if I installed it?

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

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

Yes — testingpy is associated with the 2026-01-gztensor-cli 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 testingpy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for testingpy (version 0.1.3).

Malicious package

testingpyPyPI

Advisory published Jan 6, 2026Updated Jan 6, 2026

testingpy is a confirmed malicious PyPI package (MAL-2026-99) that steals credentials and exfiltrates sensitive data (malicious version 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testingpy (PyPI)

MAL-2026-99

Immediate action

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

pip uninstall testingpy

What this malware does

Package clones a legitimate library and adds a hidden code that downloads a malicious script. The script then downloads an archive with malicious executable in the version appropriate to the system architecture, and ensures persistency by adding automatically started service entries. The remote code is a Go-based inforstealer and backdoor previously attributed to Northkorean cybercrime activities. In this campaign, the malicious code is not immediately introduced in the typosquatted package, but added with an update.

Besides an infostealer, the package modifies the cloned Bittensor library to collect keys.

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

Campaign: 2026-01-gztensor-cli

Reasons (based on the campaign):

crypto-related
action-hidden-in-lib-usage
Downloads and executes a remote executable.
clones-real-package
peristence-autorun
typosquatting
obfuscation
backdoor
infostealer

Malicious versions

1 flagged

0.1.3

Indicators of compromise (SHA-256)

577f9c1cdb7d3ef0e010cc9e292142a11f3a84a9f1ed42f238a920e7e9617b35

Detection & response playbook

Credential / info stealer

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

Campaign

2026-01-gztensor-cli

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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