Which versions of btcli-security are malicious?

The following PyPI versions of btcli-security are flagged malicious: 1.1.0, 1.1.1, 1.1.2. Treat any of these as compromised.

How do I remediate btcli-security if I installed it?

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

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

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

Malicious package

btcli-securityPyPI

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

MAL-2026-162

Immediate action

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

pip uninstall btcli-security

What this malware does

Package clones a legitimate bittensor-cli 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. Additionally, the library is modified to save sensitive keys in plaintext for further extraction

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

3 flagged

1.1.01.1.11.1.2

Indicators of compromise (SHA-256)

a4b868f818b1a81f5fccee1967f70c3ff9d75c218d14ec09882c576a9c2c213e

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 btcli-security (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging btcli-security across your stack and pipelines.
If you installed it — respond
btcli-security 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 btcli-security 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 btcli-security 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. btcli-security on PyPI has been identified as a malicious package (versions 1.1.0, 1.1.1, 1.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 btcli-security-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