Which versions of bo3to are malicious?

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

How do I remediate bo3to if I installed it?

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

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

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

Malicious package

bo3toPyPI

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

MAL-2024-11538

Immediate action

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

pip uninstall bo3to

What this malware does

During installation, a cryptominer is secretly installed and started.

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

Campaign: 2024-09-bondonioanderas-cryptominer

Reasons (based on the campaign):

cryptominer
The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

3ba9ceb66c2089feb9d9d1ba7b36c9218a396746fa3f82c811e5145e043715a2

f56f645ce4e6f0ba4962a7a5a3498c6e10a065bebb5cd57436fad8b210961a0e

131072b5bfcd4ce6218aaec66423046b83d0e49904d5992b26192daa201421bd

636ebc80ca4935056f9f0f5f5e8c0b69a5727b86efce292f9a9bf60452dbf8f2

07b4becdeaaa8939ea320caf4ba80f43af698515df3a9f3b9f7960e33cc55762

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 bo3to (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bo3to across your stack and pipelines.
If you installed it — respond
bo3to 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 bo3to 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 bo3to 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. bo3to 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-109832024-09-bondonioanderas-cryptominerRLUA-2026-00152

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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