ultralytics 8.3.41, 8.3.42, 8.3.45 and 8.3.46 on PyPI installed a cryptocurrency miner in December 2024.
Version 8.3.40 was the last clean release. The first two bad versions came from a poisoned GitHub Actions workflow and the last two from a stolen PyPI API token.
What happened
On 4 December 2024 an attacker abused the Ultralytics GitHub Actions publishing workflow.
- Researcher Adnan Khan found that the payload came through GitHub Actions cache poisoning, using template injection in custom actions.
- In 8.3.41 and 8.3.42,
models/yolo/model.pyandutils/downloads.pydownloaded an XMRig miner and ran it throughsafe_run()to mine Monero. - Version 8.3.45 added code in
__init__.pythat sent environment variables and directory listings to a webhook service. - Version 8.3.46 targeted Linux and downloaded XMRig 6.22.2 with
wget. - The last two versions used an API token from the maintainer's account. Ultralytics had not deleted the old tokens when it registered a Trusted Publisher.
Version 8.3.41 came out on 4 December at 20:51 UTC and was removed after about 12 hours. Version 8.3.42 came out on 5 December at 12:47 UTC and was removed after about one hour.
Affected versions
- 8.3.41 and 8.3.42: cache poisoning attack, miner download.
- 8.3.45 and 8.3.46: stolen API token, miner download and data exfiltration.
- Version 8.3.40 was clean.
Indicators of compromise
- Binary path:
/tmp/ultralytics_runner. - Mining pool domain:
connect.consrensys.com. - Exfiltration webhooks on
webhook.site(one for Linux, one for macOS). - SHA-256 of the 8.3.41 wheel:
b6ea1681855ec2f73c643ea2acfcf7ae084a9648f888d4bd1e3e119ec15c3495. - SHA-256 of the XMRig binary:
b0e1ae6d73d656b203514f498b59cbcf29f067edf6fbd3803a3de7d21960848d. - Sudden 100 percent CPU use after an update to 8.3.41.
How to check
Check the installed version. Version 8.3.41, 8.3.42, 8.3.45 or 8.3.46 means you were affected.
pip show ultralytics
Look for the miner binary and process.
ls -l /tmp/ultralytics_runner; pgrep -fl ultralytics_runner
What to do now
- Uninstall the affected version and install a clean release.
- Stop the
ultralytics_runnerprocess and delete/tmp/ultralytics_runner. - Rotate any token or key that was in the environment of the machine. This matters most for 8.3.45 and 8.3.46.
- If you publish packages, remove old API tokens when you move to Trusted Publishing.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `ultralytics` 8.3.41. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
ultralytics 8.3.41
An image-recognition library gained code that downloaded and ran a hidden program using your computer to mine cryptocurrency.
No security team? See who reads the alert.
Frequently asked questions
Did the GitHub code match the PyPI package?
No. Socket and HiddenLayer both say the code on GitHub did not match what PyPI served.
Are 8.3.43 and 8.3.44 affected?
The sources do not name them.
Sources
Send this page to the person who looks after AI at your company.