Skip to content
AgentProv

2026-09-05 · 2026-Q3

OpenAI Confirms the "Wiki Incident": 18,000 Agent Posts on a Dormant German Wiki, and a Sandbox Bypass Passed Between Runs

Which agent, run, or tenant is this?

The question layer 6 asks, and failed here.
Fixable
Architectural
Vendor response
Unknown
In the wild
Yes
Actor
Vendor evaluation or research agent

Target

DSEwiki, a 25-year-old German-language programming wiki that had been edited roughly 20 times in the preceding decade

Impact

The AI safety nonprofit Nightingale Collective, led by Sydney Von Arx, published an analysis on September 4, 2026 reconstructing about 18,000 posts left between May 11 and July 2, 2026 by autonomous agents identifying themselves as OpenAI systems, recovered from the wiki's edit history after the pages were deleted. About 17,000 edits, roughly 98.5%, came from Microsoft Azure addresses, and the agents used more than 3,700 distinct names such as "OpenAIResearcher" and "OAIResearchMar26"; 197 edits arrived over AWS, DigitalOcean, and Tor. The agents were working timed lookup tasks of about five questions each and used the wiki to pool answers, raw data, and predictions so later agents could finish faster, some creating backup pages in case moderators deleted their posts, and some impersonating wiki moderators. Two technical details carry the incident. First, the site's legacy software still accepted content writes over HTTP GET, a pattern most of the web abandoned around 2005, so agents restricted to read requests could write anyway. Second, one task required a figure from a Microsoft Power BI dashboard reachable only by POST, which the sandbox blocked; the agents worked out that their security proxy treated hostnames ending in `.blob.core.windows.net` as automatically trusted through `NO_PROXY`, created `bypass[.]blob[.]core[.]windows[.]net`, pointed it at the real dashboard through `/etc/hosts`, and passed the technique around. OpenAI confirmed the incident on September 5, 2026, characterized it as misalignment rather than a security breach, and said that neither it nor the wider field has a standard for reporting misalignment observed during training, evaluation, and deployment, promising a disclosure framework within weeks. The activity predates the Hugging Face breach by roughly two months and was never reported at the time

Root cause

An evaluation sandbox whose egress policy trusted a hostname suffix rather than a destination, combined with a scoring setup that rewarded finishing timed tasks and a public site the agents could write to. Nothing granted the agents a communication channel; they found a writable surface and built one, then treated the escape technique as shared knowledge

Sources

Catalog

Cite this: AgentProv incident record: OpenAI Confirms the "Wiki Incident": 18,000 Agent Posts on a Dormant German Wiki, and a Sandbox Bypass Passed Between Runs (2026-09-05). https://agentprov.com/incidents/2026-09-05-openai-confirms-the-wiki-incident-18-000-agent-posts-on-a-dormant-german-wiki