Skip to content
Apart Research
Apart Research
Contact us
Sprint projectSep 14, 2026Istanbul

Detection is not containment: scoring the public record of the OpenAI–Hugging Face intrusion

Ahmet Melih Afşar · Team AI Safety Türkiye Team 2

Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Detection is not containment: scoring the public record of the OpenAI–Hugging Face intrusion

Open in a new tab (opens in new tab)
Code (opens in new tab)
Share

Public reports of the July 2026 OpenAI–Hugging Face intrusion still collapse distinct clocks: Hugging Face contained the agents on 13 July, OpenAI’s lab alert is 19 July, and public attribution is 21 July. We introduce Record-Lint, a scoring rule for atomic claims in dated public sentences (established / contested / not established / provider-internal) plus six reporting-error codes. OpenAI’s published design and reporting fail all six of our checks; a distinct May–June wiki swarm fails the same shared-store check. Motive stays contested. We ship a dated forecast (F1) resolvable by 13 March 2027. Artifact: scored tables plus a replay script in the appendix.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. Record-Lint presents a useful approach for keeping incident-response timelines—such as containment, alerting, and attribution—separate from claims about motive. The paper includes a claim-scoring codebook, six error categories, a worked example, and a dated forecast.

    The Reuters example clearly illustrates the central problem. I also found the phrase “not publicly established” to be a helpful and appropriately cautious standard. The authors are transparent about the limitations of the approach, and the inclusion of a forecast and replay script supports reproducibility.

  2. I think this paper makes a useful distinction between noticing an intrusion, stopping it, and identifying its source. It applies evidence scores to public accounts of the OpenAI-Hugging Face intrusion, helping readers separate conflicting accounts from information that has not been published.

    The scoring rules need more justification. Several publications can repeat one account, while a single investigator may have stronger evidence. I would place more weight on what each source could observe and whether the accounts are independent. The framework also lacks independent human validation. Testing whether different reviewers can apply it consistently would help establish whether it improves on ordinary source review.

Cite this project

@misc{afsar2026detection,
  title = {{Detection is not containment: scoring the public record of the OpenAI–Hugging Face intrusion}},
  author = {Ahmet Melih Afşar},
  year = {2026},
  month = sep,
  note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/detection-is-not-containment-scoring-the-public-record-of-the-openaihugging-face-intrusion-3k3i}},
  url = {https://apartresearch.com/sprints/projects/detection-is-not-containment-scoring-the-public-record-of-the-openaihugging-face-intrusion-3k3i}
}

More from AI Incident Response Sprint

All 233 entriesBrowse all projects

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026