Who holds each part of the incident record

Figure 6 of 7 in the incident briefingRetrieved

Conceptual trust boundary and review layers

Only Hugging Face's host evidence, and the host response record that leads into it, are marked verified. This conceptual drawing places each part with the party that holds it.

  • Caution: the briefing does not mark this part or link verified
  • Verified link
  • Caution link
  • Hatched background: the research environment OpenAI says the activity left
Conceptual trust boundary and review layersA conceptual drawing of seven parts of the incident record, each placed in the lane of the party it belongs to. OpenAI reports a sequence from its research and evaluation environment, drawn as a boundary, to reported activity on Hugging Face production systems. Hugging Face's host response record, the one link marked verified, leads to its host evidence on containment, reconstruction and the affected-asset assessment, the one part marked verified. From the host evidence, a separate company review leads to OpenAI's investigation, control changes and evaluations, and evidence supplied for bounded review leads to the METR and Redwood analysis with access limits. From the company response, vendor remediation context leads to the JFrog statement and advisory, and a legal inquiry with no liability finding leads to Alabama's investigation and records demands. Every other part and link is marked caution, drawn with a dashed ink edge. The arrows show how the sources relate the parts, and the diagram makes no causal claim.OpenAIHugging FaceMETR and RedwoodJFrogState of Alabamacompany-reportedsequencehost response recordseparatecompanyreviewevidencesupplied forbounded reviewvendor remediation contextlegal inquiry, no liability findingResearchenvironmentCautionReportedcrossingper OpenAICautionHostevidenceVerifiedCompanyresponseCautionIndependentanalysisCautionVendorremediationCautionOpen legalprocessCaution Conceptual trust boundary and review layersA conceptual drawing of seven parts of the incident record, each placed in the lane of the party it belongs to. OpenAI reports a sequence from its research and evaluation environment, drawn as a boundary, to reported activity on Hugging Face production systems. Hugging Face's host response record, the one link marked verified, leads to its host evidence on containment, reconstruction and the affected-asset assessment, the one part marked verified. From the host evidence, a separate company review leads to OpenAI's investigation, control changes and evaluations, and evidence supplied for bounded review leads to the METR and Redwood analysis with access limits. From the company response, vendor remediation context leads to the JFrog statement and advisory, and a legal inquiry with no liability finding leads to Alabama's investigation and records demands. Every other part and link is marked caution, drawn with a dashed ink edge. The arrows show how the sources relate the parts, and the diagram makes no causal claim.company-reportedsequencehost responserecordseparatecompany reviewOpenAIResearch environmentCautionHugging Face, perOpenAIReported crossingCautionHugging FaceHost evidenceVerifiedOpenAICompany responseCautionMETR and RedwoodIndependent analysisFrom host evidence:supplied for boundedreviewCautionJFrogVendor remediationFrom companyresponse: vendorremediation contextCautionState of AlabamaOpen legal processFrom companyresponse: legalinquiry, no liabilityfindingCaution

Use the arrow keys to move between parts. Press Enter on a part to open its row in the table under How we know, and Escape to come back.

Ringed: the host evidence.

The arrows show how the sources relate the parts. They make no causal claim.

  1. OpenAI reports that activity crossed from its research and evaluation environment to Hugging Face production systems.
  2. Hugging Face's own system records cover how it contained the activity, how it pieced events back together and which assets were affected.
  3. OpenAI reports its own investigation, control changes and evaluations.
  4. METR and Redwood analyzed the evidence they were given for a limited review, and they report limits on their access.
  5. JFrog's statement and its advisory give context on the vendor fixes.
  6. As of 26 August 2026, Alabama's investigation and records demands were an open legal process, and the inquiry had made no liability finding.
How we know
What this figure does not prove
The diagram does not establish a complete technical path, traffic volume, probability, intent, severity, control effectiveness, liability, or universal agent behavior.
Uncertainty
The drawing lines up the layers the sources report. It is not a complete architecture or control inventory. Each part traces back to its source family.
States
The briefing's figure record gives each part and link one of two states, verified or caution, and gives no further definition of caution. This page draws caution with a dashed ink edge and an ink hatch, so the only color on the drawing marks the one verified part.
Method
The drawing stays conceptual. It leaves out reusable technical instructions, secret indicators and sensitive infrastructure detail. Each part sits in the lane of the party it belongs to. Every link is drawn at the same width, so none looks more important than another. Every link and part carries a text label and a state label, so color is never the only cue.
Tally
Every part and link in the drawing, with its party, evidence, source and state.
Part or linkKindPartyWhat it holdsEvidenceSourceState
Research environmentPartOpenAIOpenAI research and evaluation environmentOpenAI company reportThe Hugging Face incident and the road ahead (OpenAI); OpenAI Hugging Face incident technical report (OpenAI)Caution
Reported crossingPartHugging Face systems, per OpenAIReported activity on Hugging Face production systemsOpenAI company reportThe Hugging Face incident and the road ahead (OpenAI); OpenAI Hugging Face incident technical report (OpenAI)Caution
Host evidencePartHugging FaceHost containment, reconstruction, and affected-asset assessmentHugging Face host telemetrySecurity incident, July 2026 (Hugging Face); Agent intrusion technical timeline (Hugging Face)Verified
Company responsePartOpenAIOpenAI investigation, control changes, and evaluationsOpenAI company reportThe Hugging Face incident and the road ahead (OpenAI); OpenAI Hugging Face incident technical report (OpenAI)Caution
Independent analysisPartMETR and RedwoodMETR and Redwood analysis with access limitsMETR and Redwood independent investigationOpenAI and Hugging Face incident investigation (METR and Redwood Research); OpenAI and Hugging Face incident investigation mirror (Redwood Research)Caution
Vendor remediationPartJFrogJFrog statement and advisory contextVendor remediationJFrog and OpenAI collaboration on zero-day security findings (JFrog); JFrog security advisories (JFrog)Caution
Open legal processPartState of AlabamaAlabama investigation and records demandsLegal processAttorney General Marshall launches investigation into OpenAI and Sam Altman (Alabama Attorney General); Subpoena duces tecum 26-0007 (Alabama Attorney General)Caution
From company response to open legal processLinkNone in the recordLegal inquiry, no liability findingLegal processAttorney General Marshall launches investigation into OpenAI and Sam Altman (Alabama Attorney General); Subpoena duces tecum 26-0007 (Alabama Attorney General)Caution
From company response to vendor remediationLinkNone in the recordVendor remediation contextVendor remediationJFrog and OpenAI collaboration on zero-day security findings (JFrog); JFrog security advisories (JFrog)Caution
From host evidence to company responseLinkNone in the recordSeparate company reviewOpenAI company reportThe Hugging Face incident and the road ahead (OpenAI); OpenAI Hugging Face incident technical report (OpenAI)Caution
From host evidence to independent analysisLinkNone in the recordEvidence supplied for bounded reviewMETR and Redwood independent investigationOpenAI and Hugging Face incident investigation (METR and Redwood Research); OpenAI and Hugging Face incident investigation mirror (Redwood Research)Caution
From reported crossing to host evidenceLinkNone in the recordHost response recordHugging Face host telemetrySecurity incident, July 2026 (Hugging Face); Agent intrusion technical timeline (Hugging Face)Verified
From research environment to reported crossingLinkNone in the recordCompany-reported sequenceOpenAI company reportThe Hugging Face incident and the road ahead (OpenAI); OpenAI Hugging Face incident technical report (OpenAI)Caution
Sources
Source documents
Check it yourself
The figure data holds every part, link and source id in machine-readable form.

Figure 6 of 7 in the briefing

Retrieved