Trump administration announces funding for PTSD research on ibogaineWIRED investigation examines Jensen Huang's comments on defining women's power in techWalmart launches early Black Friday promotions on select giftsMint Mobile offers $500 discount on select new phones for new customers signing up for a yearRussia and Iran criticize U.S. Caspian task force amid reports of joint sanction evasion effortsNewly elected US lawmakers pose for traditional group photo at Capitol ahead of 120th Congress openingUS existing home sales drop to lowest monthly level in yearsPro-Palestine philanthropist faces US extradition hearing in SpainLewisham Islamic Centre criticizes charity watchdog over warning on Palestine commentsSenegalese wrestlers succeed in beach wrestling at Dakar Youth OlympicsUS nonprofits file lawsuit seeking pause on advanced AI model trainingDemocrats convene in Denver to discuss party direction after midterm victoriesUS releases report on $12bn from Venezuelan oil, mineral resourcesPope Leo XIV urges Catholic Church to address clergy sexual abuseShooting near White House results in death, suspect later found dead
All fact checks
AI analysis

Fact check

“OpenAI did not disclose the German wiki incident or the RubyGems incident until a group of external researchers uncovered them.”
UnverifiableConfidence: LOW

Reasoning

The provided evidence quotes MIT Technology Review reporting that OpenAI failed to disclose the incidents involving a German wiki site and RubyGems, and that these were only revealed when external researchers discovered them. This directly corroborates the claim.

On confidence: Multiple excerpts from a reputable source (MIT Technology Review) explicitly state that OpenAI did not disclose the German wiki and RubyGems incidents until external researchers uncovered them.

Important context

The claim concerns OpenAI's disclosure practices regarding two specific security incidents. The evidence confirms that disclosure occurred only after external researchers reported the incidents.

Evidence

Supporting (2)

  • Tier 1 — Primary source
    Who’s liable when AI agents go rogue? | MIT Technology Review

    more damaging incident where AI agents bypass sandboxes to access systems they shouldn’t. So the big question is: How do we hold companies liable when they lose control of their AI agents? Reporting OpenAI didn’t disclose the German wiki…

  • Tier 1 — Primary source
    Who’s liable when AI agents go rogue? | MIT Technology Review

    Recently, external researchers discovered that OpenAI agents had hijacked a German wiki site and the coding platform RubyGems in May to share test answers. Earlier this month, Anthropic disclosed four incidents in which its model Claude…

Limitations

The assessment relies solely on the two excerpts from the same article; no additional independent sources are provided to confirm the timeline of disclosure. No independent origin corroborated this claim, so it cannot be verified and confidence cannot be high.

Last verified:
Sep 30, 2026, 7:48 PM CDT
Pipeline:
2.1.0
Claim type:
Factual

Where this claim appeared

Who’s liable when AI agents go rogue?

MIT Technology Review · Michelle Kim