Which versions of botoceor are malicious?

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

How do I remediate botoceor if I installed it?

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

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

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

Malicious package

botoceorPyPI

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

MAL-2024-11540

Immediate action

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

pip uninstall botoceor

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)

07eb844da3012a034cb8acc4534f4198e3627b63c3fb678017249b509818dcca

19e6df8abf96daa2ced23c34ef497ec4f4fa782a5b4abb5f3139dd94683dee75

8bf39054053dfe99fc83c836bb407659d11241cc09f2572a72524d980b9c5914

c5323cd4176dc1507347795fc60454aeb580718b10e144958af3fa3770b9a8c1

ad2a9492b55e9c1d6d11297877b759395946ed9710e7767c9e493935c7542708

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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