Which versions of python-bittensor-config-v2 are malicious?

The following PyPI versions of python-bittensor-config-v2 are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate python-bittensor-config-v2 if I installed it?

python-bittensor-config-v2 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 python-bittensor-config-v2 — how do I know if it already compromised me?

If python-bittensor-config-v2 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 python-bittensor-config-v2 part of a known attack campaign?

Yes — python-bittensor-config-v2 is associated with the 2026-05-ninja-ssh-proto 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 python-bittensor-config-v2 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 python-bittensor-config-v2 (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-bittensor-config-v2 across your stack and pipelines.

Malicious package

python-bittensor-config-v2PyPI

Malicious code in python-bittensor-config-v2 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3402

Immediate action

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

pip uninstall python-bittensor-config-v2

What this malware does

During installation or import, package silently adds a new authorized SSH key. It's closely related to the 2026-05-ninja-core-utils campaign, but there is no built-in crypto exfiltration.

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

Campaign: 2026-05-ninja-ssh-proto

Reasons (based on the campaign):

backdoor
obfuscation

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

6f2ecdbc9e024d6dc51c8e5d48941c5aac432db65ad733317aed159d480973cd

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 python-bittensor-config-v2 (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-bittensor-config-v2 across your stack and pipelines.
If you installed it — respond
python-bittensor-config-v2 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 python-bittensor-config-v2 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 python-bittensor-config-v2 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. python-bittensor-config-v2 on PyPI has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-ninja-ssh-proto

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks python-bittensor-config-v2-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