Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

yolov8miniPyPI

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

MAL-2025-3484
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall yolov8mini

What this malware does

On importing the module, there is an automated start of a Telegram bot capable of exfiltrating passwords from browsers, executing arbitrary commands and so on. While the description states it's a monitoring tool, the automated start, capabilities targeting secret values suggest malicious intentions.

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

Campaign: 2025-03-yolov8mini

Reasons (based on the campaign):

  • infostealer

  • exfiltration-generic

  • dependency-confusion

  • exfiltration-browser-data

  • The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

10 flagged
0.10.1.11.1.11.2.11.3.11.4.12.0.12.1.12.2.12.3.1

Indicators of compromise (SHA-256)

1dc0eb3e828547e3984fc6ee95459f3948326df479784f46b7f9e43b0893876f
07aef48176f15d2a6458d10e86017e8c8d5e1dff8bf1852f9aa362cb904ff3b2
a9222d20b84ed716d5bdf81f1da1d0f088fc7482894c8f25a5d1f757cc477ba9
68e19b0d45f92b02ef259a281ccb9a76766b7aea9c7edec8adf8393fa59650a5
ad099f2f31ac262b494a75650849dc9704229bddd64a022050034107c55fb8a6
6863dc3f3b79bbe20284e48253503154e8f1ec8793b2c77b0a0bd523d4647520

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for yolov8mini (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yolov8mini across your stack and pipelines.

  2. If you installed it — respond

    yolov8mini 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.

  3. Did it already run?

    If yolov8mini 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.

  4. How O3 protects you

    O3 blocks yolov8mini 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. yolov8mini on PyPI has been identified as a malicious package (versions 0.1, 0.1.1, 1.1.1, 1.2.1, 1.3.1, 1.4.1, 2.0.1, 2.1.1, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025522025-03-yolov8miniRLUA-2026-00941RLUA-2026-02086

References

Credits

  • Kamil Mańkowski (kam193)
  • ReversingLabs · finder

Detect & block this

O3 blocks yolov8mini-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

yolov8mini (PyPI) malicious package — MAL-2025-3484 | O3 Security