Which versions of gztensor-cli are malicious?

The following PyPI versions of gztensor-cli are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate gztensor-cli if I installed it?

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

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

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

Malicious package

gztensor-cliPyPI

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

MAL-2026-53

Immediate action

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

pip uninstall gztensor-cli

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 Nordkorean cybercrime activities.

The malicious code was introduced in version 0.1.1. 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

6 flagged

0.0.10.0.20.0.30.0.40.1.10.1.2

Indicators of compromise (SHA-256)

19f3c00d7a3a1b03a4524168199226aa56d2a86086aeabb3ef3f1fc860f10973

9849e93934366bce1507e103687b8777fc90358a35173ff44ad34dc9b871c644

6010189e23e54782200df770b6e40ed7e37284779c25f28cd145aadd9ee8b623

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 gztensor-cli (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gztensor-cli across your stack and pipelines.
If you installed it — respond
gztensor-cli 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 gztensor-cli 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 gztensor-cli 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. gztensor-cli on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.1.1, 0.1.2 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 gztensor-cli-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