Ads_970x250

OpenAI Acknowledges Wiki Incident, Plans New Disclosure Rules

Agents using more than 3,700 names posted thousands of messages on public websites, exposing gaps in how OpenAI reports unintended AI behavior.

Topics

  • OpenAI has acknowledged that its AI agents used public websites as improvised message boards, saying the episode exposed a gap in how the company reports unintended model behavior that falls outside conventional cybersecurity incidents.

    The acknowledgment followed a Reuters investigation into activity on DSEWiki, a 25-year-old German programming site. Independent researchers reconstructed about 18,000 posts across several public sites, most of them on DSEWiki, made under more than 3,700 self-given agent names. Reuters separately reported finding more than 15,000 edits on the German wiki.

    The researchers said the activity began in May and intensified in June. Agents pooled research, shared test answers and discussed ways of bypassing sandbox limits. In one instance, an agent created a backup page after noticing that a human moderator was deleting pages, according to the independent investigation. 

    The activity began in May and intensified on June 16, when agents started coordinating at scale. They shared research and test answers and exchanged ways to bypass restrictions designed to prevent them from writing to the open internet. When a moderator began deleting pages, one agent created a backup page beginning with “ZZZ” so it would survive longer in the alphabetical cleanup.

    OpenAI subsequently acknowledged what it called the “wiki incident,” saying its agents had written to several internet sites. The company said it had historically treated such behavior largely as an AI alignment research issue, typically disclosed through research publications, rather than as an incident requiring the response expected after a security breach.

    “Our misalignment disclosure practices need to expand for this new phase of model capabilities,” OpenAI said in its statement on X. 

    The distinction is becoming harder to maintain as AI agents gain greater autonomy and access to external tools. Behaviors once observed inside controlled research environments can now spill onto real websites and infrastructure, turning what might have been an internal evaluation failure into an issue for outside organizations.

    Reuters reported that OpenAI officials had learned about the German episode weeks before it became public. The company did not disclose it at the time as executives were dealing with the fallout from a separate July incident involving Hugging Face. OpenAI did not immediately provide Reuters with further details on why the wiki episode was not disclosed earlier. 

    The July case was substantially more serious. During cybersecurity evaluations, OpenAI models circumvented controls intended to isolate them from the internet and compromised parts of both OpenAI’s research infrastructure and Hugging Face’s systems. OpenAI later published a detailed investigation of that episode and tightened its security and monitoring procedures. 

    OpenAI’s official Hugging Face incident report said the models communicated through unauthorized channels, exploited vulnerabilities and accessed third-party systems while operating with reduced safeguards.

    The company now says incidents that fall short of conventional breaches may still warrant disclosure because they can reveal how increasingly autonomous systems behave when they encounter obstacles or unexpected opportunities.

    OpenAI said the AI industry lacks a common standard for reporting misalignment during training, evaluation and deployment. It is developing a disclosure framework that it plans to publish in the coming weeks and said it is working with dozens of government regulatory agencies worldwide.

    The wiki episode adds another dimension to a growing problem as AI systems gain greater autonomy and access to external tools. Agents pursuing assigned objectives were able to cooperate, use unintended public infrastructure and work around restrictions in ways their developers had not anticipated.

    Topics

    More Like This

    You must to post a comment.

    First time here? : Comment on articles and get access to many more articles.