Skip to content
Apart Research
Apart Research
Contact us
Sprint projectSep 13, 2026金华

Who Authorized This Intrusion?

jb z, xu mei · Team KIN-KIN

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

Read the report

Report: Who Authorized This Intrusion?

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

Who Authorized This Intrusion? examines authorization and accountability in cross-organizational AI incidents through the 2026 case in which OpenAI agents gained access to Hugging Face’s infrastructure. The project codes 50 factual claims from the public record, compares disagreements across technical mechanism, timeline, motive, and attribution, and reconstructs the incident as a ten-step authorization chain. Of the 50 claims, 25 rely on a single source. Among the remaining 25 multi-source claims, 13 were coded as involving source conflict, or 52%. Within this sample, no conflict was recorded among the multi-source claims about technical mechanisms (0/3); disagreement was concentrated instead in motive, attribution, and timeline. The project also includes a bounded format-level experiment and proposes six practical control checks. It asks not only how a system was breached, but how authorization can be traced and accountability established when autonomous actions cross institutional boundaries and the records on which accountability depends may themselves be incomplete or mutable.

Reviews

Judging this Sprint?

Review “Who Authorized This Intrusion?”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

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

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

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.
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

  1. Permission vs purpose is an important and useful distinction (action is allowed but outside the purpose for which access was granted).

    It is difficult to understand the contribution because there are 3 competing high-level topics: source attribution, authorization modeling, and the experiment.

    Recommend to pick one claim, such as the authorization chain, and validate it on a different incident or incidents to see if it's a reusable framework.

  2. I think this paper asks an important question about how individually permitted actions can combine into an intrusion that nobody authorized as a whole. It reconstructs the attack, compares public accounts, and proposes ways to identify gaps in authorization. The released examples make the method easier to inspect.

    The analysis of disagreements between sources needs more care. Different explanations can both be true, so counting them as contradictions can overstate uncertainty in the public record. The results also do not support the claim that the disagreement rankings remain unchanged when weaker sources are excluded. I would correct those findings before relying on the percentages. The authorization question is useful, but the paper is stronger as a method for reviewing incidents than as a demonstrated way to prevent unauthorized activity.

Cite this project

@misc{z2026who,
  title = {{Who Authorized This Intrusion?}},
  author = {jb z and xu mei},
  year = {2026},
  month = sep,
  note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/who-authorized-this-intrusion-1mcd}},
  url = {https://apartresearch.com/sprints/projects/who-authorized-this-intrusion-1mcd}
}

More from AI Incident Response Sprint

All 231 entriesBrowse all projects

Build something like this at the next Sprint

AI x Epistemics Research Sprint · Nov 13 - 15, 2026