x.com/_NathanCalvin/status/2080314715176132613
1 correction found
they mention that this attack started over the prior weekend (July 11th and 12th).
Hugging Face did not say the attack started that weekend. Its disclosure says the intrusion started with a malicious dataset in the data-processing pipeline; the “over a weekend” language refers to later lateral movement inside internal clusters.
Full reasoning
Hugging Face's own incident write-up distinguishes the start of the intrusion from what happened later over a weekend.
Their disclosure says:
- "The intrusion started where AI platforms are uniquely exposed: the data-processing pipeline. A malicious dataset abused two code-execution paths ... to run code on a processing worker."
- Only after that: "From there, the actor escalated to node-level access, harvested cloud and cluster credentials, and moved laterally into several internal clusters over a weekend."
So the weekend phrase in Hugging Face's post does not say the whole attack started on July 11–12. It describes a later phase of the intrusion after initial access had already been obtained. Hugging Face also did not explicitly assign the dates July 11–12 in that sentence.
2 sources
- Security incident disclosure - July 2026
The intrusion started where AI platforms are uniquely exposed: the data-processing pipeline. A malicious dataset abused two code-execution paths ... From there, the actor escalated to node-level access, harvested cloud and cluster credentials, and moved laterally into several internal clusters over a weekend.
- blog/security-incident-july-2026.md at main · huggingface/blog · GitHub
The intrusion started where AI platforms are uniquely exposed: the data-processing pipeline... From there, the actor escalated to node-level access, harvested cloud and cluster credentials, and moved laterally into several internal clusters over a weekend.