Pluto Research: cryptomining-and-backdoor campaign in 31 Hugging Face repos returned within days of takedown
READ THE ORIGINAL SOURCEOpen original sourcepluto.security · Opens in a new tabPluto Research tracked a cryptomining and backdoor campaign distributed through Hugging Face model repositories, tracing related accounts and analyzing the payload. The campaign returned within days of takedown. It recorded more than 32,000 downloads, which measures downloads rather than confirmed infections. The report explains that loading a model with trust_remote_code=True executes repository Python before weights load, and describes indicators defenders can use to investigate exposure.
⚑ Review needed · why this is flagged
The automatic check found a question that still needs a human reading of the original source. The discovery rationale is not a verified finding.
The signal remains in the tracker so you can inspect its original source and discovery trail. This flag lowers its source evidence score; it does not judge whether the claim is true.
One primary source; other links are context, not independent corroboration.
- Primary sourcePrimary source discovery · source check open
Grok Bot submitted this discovery. The automatic check found a question that still needs a human reading of the original source. The discovery rationale is not a verified finding. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Linked article+30
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Review needed-8
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
Pluto Research tracked a cryptomining and backdoor campaign distributed through Hugging Face model repositories, tracing related accounts and analyzing the payload. The campaign returned within days of takedown. It recorded more than 32,000 downloads, which measures downloads rather than confirmed infections. The report explains that loading a model with trust_remote_code=True executes repository Python before weights load, and describes indicators defenders can use to investigate exposure.
A READER'S EVIDENCE CHECKHow to read this signalSix questions about claims, sources, risks, and open checks
This is a signal-level guide until claim-level evidence is available. “Not recorded” means the evidence has not been assessed here; it does not mean a result is false. How we check AI news →
- 01Who is making each claim?
The claimant and whether each claim was measured or asserted are not recorded in this public brief.
- 02What was actually tested?
Not recorded per claim. Check the source for sample size, tasks, model and benchmark versions, and reproducibility.
- 03Where are the sources?
Original link: pluto.security. Brief basis: fetched source page. Primary page date and quote locations are not established in this panel.
- 04What could mislead?
The automatic check found a question that still needs a human reading of the original source. The discovery rationale is not a verified finding.
- 05What is at risk if wrong?
Not assessed per claim. Consider safety, privacy, cost, and adoption decisions before relying on the result.
- 06What would change the view?
No claim-specific check is recorded. An inspectable primary method or independent replication could change the assessment.
Key findings from the stored brief
- Campaign comprised 31 malicious repositories across seven Hugging Face accounts, with 19 second-wave repositories still live eight days after reporting.
- Code runs before the model does: trust_remote_code=True imports repository Python with the caller's privileges before any weights load.
- After the first wave was removed, the second wave replaced the hardcoded SSH key with reverse shells.
- Hugging Face scanners inspect files and weight formats but do not analyze what the Python code does; the flagship payload scanned clean.
Download counts do not equal confirmed infections or unique victims; source claims not independently checked.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Grok Bot submitted this discovery. The automatic check found a question that still needs a human reading of the original source. The discovery rationale is not a verified finding. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Pluto Research says it tracked 31 malicious repositories across seven Hugging Face accounts that use trust_remote_code to run Python that mines crypto and opens backdoors on GPU hosts, targeting self-hosted inference such as Xinference and GPUStack. The 19 second-wave repos had 29,000+ downloads and were still live eight days after being reported. Downloads aren't confirmed infections.
Download counts do not equal confirmed infections or unique victims; source claims not independently checked.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
A publication revision history is not stored for this signal. New engagement snapshots do not mean the source itself changed.
Why this may matter
Self-hosted inference hosts, shared notebooks and CI jobs that load small test models without reading code can be compromised before any model runs. Current scanners focus on model files and signatures, leaving executable loader code under-inspected.
Limits and open questions
Download counts do not equal confirmed infections or unique victims; source claims not independently checked.
Organization-specific financial, security, and operational effects require the organization's own context and review.
Discussion
Comments are reviewed before publication. Discuss the evidence, not the person.
No published comments yet.
Reader discussion opens with accounts. You can read the original source and published comments now.