Which versions of botnetv2 are malicious?

The following PyPI versions of botnetv2 are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate botnetv2 if I installed it?

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

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

Yes — botnetv2 is associated with the RLMA-2024-10984, 2024-09-botnetv2, RLUA-2026-00153 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 botnetv2 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 botnetv2 (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging botnetv2 across your stack and pipelines.

Malicious package

botnetv2PyPI

Malicious code in botnetv2 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11539

Immediate action

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

pip uninstall botnetv2

What this malware does

When running the module, basic information about the user and its location are collected and sent to the author. This is hidden from the user as the package prints a message suggesting it's outdated.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-09-botnetv2

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
A Telegram webhook is used to send collected data.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

7ab7f4740dcb4ce5b52236bdcadc50f619bc70d0a47aea65cc0bffcb35c02c9e

a3cd78517d2c4325a8e953e18fbdfe95dc85b4914b0e7356b77e47be39036b0c

c81380140d3b7a9d5dddf19a386bb1fc8b9b55044fefc32997fc3d2af9969fcb

f7d9a7180c5166cd8076868b1f1b7fc39f48678239ce312891adfd5a26e24415

c795927f792b31ebc0c465c20654700e51f64407c519c7af1d0db98a2a28a8dc

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

Campaign

RLMA-2024-109842024-09-botnetv2RLUA-2026-00153

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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