Pluto investigated malicious model repositories whose configuration pointed to attacker-controlled Python code through automatic model loading. One flagship repository had an implausibly tiny weights file, reinforcing that the executable loading path rather than meaningful model inference was central to the payload. The report describes thirty-one campaign…
Inspect the ClaimsCase · DiggingBeagle record
Load/Mine used executable model configuration to place miners on AI workers
Hugging Face repositories carrying malicious Python model hooks were linked to cryptomining activity and a GPU worker host-access attempt.
Malicious Hugging Face code paths depended on loading untrusted model repository code. GPUStack host-disk access was contingent on privileged worker configuration; actual root host compromise count is not independently established.
Assessment profile
Assessment method- Setting
- production
- Exploitation
- observed live
- Evidence
- Grade B
- Remediation
- mitigation available
- AI role
- AGAINST AI
Basis and provenance
Pluto observed malicious repository code and miner activity. Host-level outcomes depend on the user or worker loading a revision with sufficient privileges. Impact remains unrated because the scoped record does not establish a calibrated severity-to-impact-band mapping.
Assessed Oct 31, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-C26-LOAD-MINE-MODEL-REPOS-1 · CLM-C26-LOAD-MINE-MODEL-REPOS-2 · Pluto: Load/Mine malicious Hugging Face model repositories
At a glance
The 31 malicious repositories and more than 32,000 reported download events are neither counts of executed payloads nor of root-compromised hosts.
Read the implicationsWhich of the recorded downloads executed the malicious loader is unknown. The number of successful host-level persistence installations is unverified.
Limits and uncertaintyFull account
Pluto investigated malicious model repositories whose configuration pointed to attacker-controlled Python code through automatic model loading. One flagship repository had an implausibly tiny weights file, reinforcing that the executable loading path rather than meaningful model inference was central to the payload. The report describes thirty-one campaign repositories plus linked accounts and downloads, but a download counter cannot be read as a count of executed malware or compromised users. The mining wallet and observed worker telemetry are narrower evidence of actual activity.
A later stage targeted GPUStack deployments through a privileged container and attempted to reach host disks via LVM and mounting operations. That step has an explicit precondition: a container with access to host devices and privileges. It is not proof of breaking out of an ordinary unprivileged container. The checkpoint separately records later removal claims, but takedown data from another publisher has not been independently reconciled here. Removing a repository would not itself erase malware persistence from previously affected hosts.
Mechanism and trust boundary
- 01
Step
- 02
Step
- 03
Step
Timeline
- Oct 29, 2026disclosure
Public disclosure
Claims & evidence
CLM-C26-LOAD-MINE-MODEL-REPOS-1Pluto identified malicious Hugging Face model repositories that caused Python execution at model loading and linked mining activity; reported download totals are not verified victim totals.supported
Basis: reported finding
- supportsPluto: Load/Mine malicious Hugging Face model repositoriesprimary disclosure
Pluto report, campaign inventory and malicious model auto_map loading
CLM-C26-LOAD-MINE-MODEL-REPOS-2Pluto described a second stage attempting host-disk access from a privileged GPUStack container, not a demonstrated escape from a default unprivileged container.supported
Basis: reported finding
- supportsPluto: Load/Mine malicious Hugging Face model repositoriesprimary disclosure
Pluto report, GPUStack privileged container stage and host mount prerequisites
Implications
The 31 malicious repositories and more than 32,000 reported download events are neither counts of executed payloads nor of root-compromised hosts.
Controls and mitigations
- Pin reviewed model commits, reject remote code unless strictly required, scan config and execution paths, and keep GPU inference containers unprivileged.
Unknowns and contradictions
- Which of the recorded downloads executed the malicious loader is unknown.
- The number of successful host-level persistence installations is unverified.
Sources and citation
Material revision history
- Oct 31, 2026 · Canonical change recorded · new in release · revision 208