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

Both Sides Detected It, Neither Escalated Concurrency and Escalation Failure in the July 2026 Autonomous Agent Intrusion

Fatimah Emad Eldin · Team Reconciliation Gates

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

Read the report

Report: Both Sides Detected It, Neither Escalated Concurrency and Escalation Failure in the July 2026 Autonomous Agent Intrusion

Open in a new tab (opens in new tab)
Presentation

Presentation: Both Sides Detected It, Neither Escalated Concurrency and Escalation Failure in the July 2026 Autonomous Agent Intrusion

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

Public accounts of the July 2026 autonomous agent intrusion frame the response failure as a detection failure. Against the published forensic record — 7 primary sources, a reproducible pipeline — detection was not the binding constraint at either organisation. The victim’s signals fired, were correlated into a coherent attack signal, and were never raised to a criticality that paged anyone. The perpetrator’s own appendix timestamps a monitoring alert at 12:03 UTC and responders halting the runs 5h34m later, with 8 further compromise events inside that interval. We argue this failure — correct class, insufficient priority — satisfies every quantity current alert-screening formalisations define, and that security, unlike process-safety alarm management, publishes no target priority distribution against which it could be measured. We also report the arithmetic bound that makes the phase-extent statistics uninformative.

Reviews

Judging this Sprint?

Review “Both Sides Detected It, Neither Escalated Concurrency and Escalation Failure in the July 2026 Autonomous Agent 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. The paper's main problem is that its big finding isn't a finding: Hugging Face already said in their own blog post that they detected the attack and failed to escalate it, and the sprint's own recruitment page describes that same problem, so the paper's opening claim that everyone thinks this was a detection failure is something it never actually shows anyone said. The rest of the quantitative work is also pretty thin - it takes a nine-row table Hugging Face published, rescales the timestamps, subtracts two numbers from OpenAI's appendix to get five and a half hours, and spends nearly half the paper building a concurrency statistic that the paper then proves is meaningless and throws away. The paper also offers no predictions, no resolvable questions, and one proposed metric it admits cannot be computed.

1 judge declined to score this project.

Cite this project

@misc{eldin2026both,
  title = {{Both Sides Detected It, Neither Escalated Concurrency and Escalation Failure in the July 2026 Autonomous Agent Intrusion}},
  author = {Fatimah Emad Eldin},
  year = {2026},
  month = sep,
  note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/both-sides-detected-it-neither-escalated-concurrency-and-escalation-failure-in-the-july-2026-autonomous-agent-intrusion-218e}},
  url = {https://apartresearch.com/sprints/projects/both-sides-detected-it-neither-escalated-concurrency-and-escalation-failure-in-the-july-2026-autonomous-agent-intrusion-218e}
}

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