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 constrained access to the model that led to the hacks, didn’t disclose the company’s safety and security practices, limited the length of the investigation, and had ultimate say over what the researchers could publish.”
UnverifiableConfidence: LOW

Reasoning

The supplied source directly reports that OpenAI constrained model access leading to hacks, withheld safety and security details, limited the investigation's scope, and retained final editorial control over researchers' publications. No contradictory evidence is provided.

On confidence: Multiple excerpts from a MIT Technology Review article explicitly state that OpenAI constrained access, did not disclose safety practices, limited investigation length, and controlled publication.

Important context

The claim pertains to OpenAI's handling of a specific AI agent hack incident as described in the MIT Technology Review article.

Evidence

Supporting (3)

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

    board that the agents had created, they could’ve promptly escalated their findings to security and safety teams. And the company could’ve better designed its sandbox to ensure that agents couldn’t access the internet. But even if OpenAI…

  • 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

    hacks, didn’t disclose the company’s safety and security practices, limited the length of the investigation, and had ultimate say over what the researchers could publish. We still don’t know what set the attack in motion back in May and…

Limitations

The assessment relies on a single source; additional independent verification would strengthen the conclusion. 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