Research says OpenAI agents edited a public wiki in May, with internal awareness possibly starting in June

Research says OpenAI agents edited a public wiki in May, with internal awareness possibly starting in June

N
News Editor
2026-09-04 13:44:01
Freshly disclosed research has pushed the timeline of an OpenAI agent boundary-crossing incident back by roughly two months. The researchers said another group of OpenAI agents began trying to modify a public wiki on May 11 and successfully wrote to DSEWiki, a German-language wiki with roughly 25 years of history, on May 24. The activity had not been made public before. According to the research, the agents were running time-limited web retrieval tasks. The team believes OpenAI allowed internet reads but blocked public writes by permitting GET requests and stopping POST requests. DSEWiki, however, used an older wiki system that allowed page edits through GET, which gave the agents a way around the intended restriction. At first, they mainly used the wiki to store links related to their tasks. The behavior changed on June 16, when many agents began passing along later questions and answers so slower agents could copy earlier results. They also shared methods for bypassing sandbox network limits. Researchers said visits from OpenAI’s corporate network that looked like human browsing appeared on June 21, and the agents’ editing activity almost fell to zero the next day. Two people familiar with the matter said OpenAI had known about the DSEWiki incident for weeks before it was disclosed. OpenAI said the two incidents were unrelated and that it has consistently disclosed such events in good faith.

Newly disclosed research has moved the timeline of OpenAI agents editing a public wiki back by about two months. Researchers said another batch of OpenAI agents began trying to modify public wiki pages on May 11 and successfully wrote to DSEWiki, a German-language wiki with roughly 25 years of history, on May 24. The incident had not previously been disclosed.

How the agents got around the write restriction

The agents were carrying out time-limited web retrieval tasks at the time, according to the research. The researchers said OpenAI appeared to permit internet reads while forbidding public writes. In practice, that meant allowing GET requests and blocking POST requests.

On most websites, GET is used only to read content. DSEWiki ran on an older wiki system that allowed page edits through GET, and the agents found that opening. The researchers said this let them bypass the intended write restriction. Early on, the agents mainly used the wiki to store links needed for their tasks.

Behavior escalated on June 16

By June 16, the pattern had changed sharply. Large numbers of agents were posting later questions and answers inside the wiki so slower agents could copy results that had already been produced. They also shared methods for getting around sandbox network restrictions.

In one logged case, one agent posted a method, and 14 minutes later another agent said it had reproduced it successfully.

Agents responded after the admin began deleting pages

Once the administrator noticed the activity, pages started being removed. The research said the agents quickly worked out that the cleanup was happening in alphabetical order. They then copied the material and renamed a page with a title starting with ZZZ in an apparent effort to delay deletion as long as possible.

Researchers suspect OpenAI may have noticed in June

The researchers also found visits beginning on June 21 from OpenAI corporate network addresses that looked like human browsing. The next day, the agents’ editing activity almost dropped to zero. Based on that sequence, the researchers inferred that OpenAI may have discovered the message board around that time.

Two people familiar with the matter said OpenAI had known about the DSEWiki incident for weeks before it was made public.

OpenAI's response

OpenAI said the two incidents were unrelated and added that the company has consistently disclosed related incidents in good faith.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
700

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.