Case · 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.

Scope

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.

At a glance

Mechanism and trust boundary

  1. 01

    Step

  2. 02

    Step

  3. 03

    Step

Timeline

  1. Oct 29, 2026
    disclosure

    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

Link to claim
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

Link to claim

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

  1. Oct 31, 2026 · Canonical change recorded · new in release · revision 208