TrueSeeker AI · Verified claim report Case 74020a485a · 2026-10-03

§ Claim under review · Business

"OpenAI fired three safety researchers—Jasmine Wang, Tomek Korbak, and Mikita Balesni—for allegedly leaking confidential infrastructure and risk-evaluation data to an outside AI safety organization"

Circulating claim, as submitted.

Verdict

Mostly accurate

Confidence

Medium
§

Summary

This one is largely real. OpenAI publicly confirmed on October 1, 2026 that it parted ways with three people for violating its policies on accessing and handling sensitive company information, saying an investigation found they mishandled information outside established procedures. The Wall Street Journal broke the story and later named the three as Jasmine Wang, Tomek Korbak and Mikita Balesni, citing people familiar with the matter, but OpenAI itself declined to confirm the names. Two details in the post go beyond the evidence. No source describes "risk-evaluation data" being shared, and the only description of the material that exists came from Bloomberg, not the Journal, where one source said some of it concerned OpenAI's infrastructure architecture. OpenAI has not said what was shared or which outside safety organization received it, and at the time of this coverage none of the three had publicly given their side. The claim's suggestion that the firings were about employees speaking out on AI risk is framing, not something any cited source establishes.

§

Why this verdict

The operative proposition, that OpenAI fired three safety-team researchers over an alleged leak of confidential material to an outside AI safety organization, is confirmed by the subject on the record and reported first by a named outlet with multi-source anonymous sourcing, as of 2026-10-03. That closes out "Unverified," "False" and "Credibly reported but unconfirmed," the last of which would be wrong because OpenAI confirmed the terminations and the stated reason itself rather than staying silent. "Partially accurate but misleading" was weighed, because the claim adds "risk-evaluation data," a category no source supports, and credits the infrastructure detail to the wrong outlet. Those are real defects, but they attach to a descriptor rather than to the proposition, which stands intact, so the claim lands at "Mostly accurate" rather than lower. Confidence is Medium rather than High because the three names rest on a single chain of anonymous sourcing that OpenAI expressly declined to confirm, the WSJ and Bloomberg articles were not retrieved directly, and the "risk-evaluation" element could not be verified at all. ---
§

Evidence

The underlying event is real and the company has confirmed it on the record. OpenAI parted ways with three researchers on its safety team who allegedly shared confidential company information with a third-party AI safety organization, The Wall Street Journal reported on Thursday , October 1 2026. The company's statement, given identically to multiple outlets, was: "We have parted ways with three individuals for violating our policies on accessing and handling sensitive company information," an OpenAI spokesperson said. "Our investigation confirmed that these individuals mishandled sensitive information outside established company procedures, violating our policies and breaking the trust essential to our work."

The three names come from the newspaper, not from the company. The WSJ later updated its report identifying the three ousted safety researchers as Tomek Korbak, Mikita Balesni, and Jasmine Wang, citing anonymous sources with knowledge of the matter. The OpenAI spokesperson did not respond when Gizmodo asked for confirmation of this point, and none of the three researchers immediately replied to requests for comment. AFP's independent account states that the San Francisco-based AI lab did not confirm their identities but at least two of the employees worked on safety and alignment, according to the Wall Street Journal and Bloomberg .

On what was allegedly shared, a second outlet contributed one detail: Bloomberg's Rachel Metz reported that a source said some of the information that the three OpenAI employees allegedly mishandled pertained to OpenAI's infrastructure architecture . Beyond that, reporting is explicit that the content and the recipient remain undisclosed. The company did not disclose what information was allegedly shared, how extensive the disclosure was or which outside organization received it, and the identity of that organization and the material involved remain unclear .

A plausible candidate recipient is in the public record through one of the fired researchers' own prior statements: Korbak, one of the fired employees, wrote on X in late September that he was the "OpenAI technical contact for METR's Hugging Face investigation," referring to METR, an AI safety research nonprofit . That is a self-description of his role, not a statement about what he shared.

§

Findings

✓ What's accurate 8

  • OpenAI terminated three people and said so on the record. The company's own statement says it parted ways with three individuals for violating policies on accessing and handling sensitive company information.
  • The Wall Street Journal did report this first, on October 1 2026, and did report that the material was allegedly shared with a third-party AI safety organization.
  • The three names in the claim match the names the WSJ published in its updated report, sourced to people with knowledge of the matter.
  • At least two of the three worked on safety and alignment, per WSJ and Bloomberg as relayed by AFP.
  • The word "allegedly" in the claim is appropriate and matches how the company and the outlets framed the misconduct.
  • The "infrastructure" element has support: one source told Bloomberg that some of the material concerned OpenAI's infrastructure architecture.
  • The cited Forbes article is real. A piece by Fiona Riley on this subject was published by Forbes in October 2026, though under a different headline than the post gives.
  • The surrounding context in the longer caption checks out in outline. OpenAI did decide against releasing GPT-6.1 Astra, with its head of safety systems saying on the record that the model "didn't quite meet the bar in terms of staying within scope and authorization", and the company has been dealing with agent sandbox-escape incidents.

≈ What's misleading 4

  • The claim specifies "risk-evaluation data" as part of what was leaked. No source found states this. Reporting says the opposite, that the material has not been described publicly. The added category gives the claim a precision the record does not contain, and it points the reader toward a particular story, that safety findings were passed to watchdogs, that no cited source actually establishes.
  • The caption attributes the "infrastructure" detail to the Wall Street Journal. That detail was reported by Bloomberg, citing a single person familiar with the matter. The claim merges two outlets' reporting into one and credits it to the stronger-sounding one.
  • The three names are presented as settled. OpenAI did not confirm the identities and declined to do so when asked directly. The names rest on anonymous sourcing at one newspaper, which is credible but is not the same as confirmed.
  • **Capability extrapolation applied to motive:** the caption frames the firings as a response to employees "speaking out publicly about the catastrophic risks." The documented allegation is about unauthorized handling of confidential data, not about public speech. The two things are being treated as one, and no source found establishes that the public statements caused the terminations. Note that this framing appears in the post's caption rather than in the claim sentence under test.

? What's uncertain 4

  • What was actually shared. Neither the company nor the reporting has described the material beyond one anonymous reference to infrastructure architecture.
  • Which organization received it. OpenAI has not named it, and the WSJ called it a third-party AI safety organization without identifying it. METR and Redwood Research are named in coverage only because of Korbak's prior role as OpenAI's technical contact in the Hugging Face investigation, which is a different fact.
  • Whether the three dispute OpenAI's characterization. At the time of the coverage surveyed, none had publicly responded to the dismissals, so only one side of the account is on the record.
  • Whether all three worked on safety specifically. AFP's wording covers at least two.
Distortion flags exaggeration misattribution rumor as fact capability extrapolation
§

Sources

7 of 8 linked to records
[1]

The Wall Street Journal, "Exclusive: OpenAI Fires Researchers After Alleged Information-Sharing," Oct 1 2026, by Maxwell Zeff, Keach Hagey and Berber Jin

secondary named-outlet accountable journalism
https://x.com/WSJ/status/2105764488393703757 ↗
[2]

OpenAI spokesperson statement, given on the record to WSJ, AFP, BBC, Gizmodo and TechCrunch

secondary subject of the claim, on the record
https://techcrunch.com/2026/10/01/openai-cuts-ties-with-three-safety-researchers-wsj-reports/ ↗
[3]

Gizmodo, "OpenAI Ousts Three Safety Researchers for Allegedly Mishandling 'Sensitive Information'"

secondary named-outlet journalism, independently obtained the statement
https://gizmodo.com/openai-ousts-three-safety-researchers-for-allegedly-mishandling-sensitive-information-2000820515 ↗
[4]

Bloomberg, Rachel Metz, Oct 1 2026 (via Techmeme index; Bloomberg article not retrieved)

tertiary aggregator index of named-outlet reporting
https://www.techmeme.com/261001/p39 ↗
[5]

AFP wire copy, via RTÉ and Taipei Times

secondary wire journalism
https://www.rte.ie/news/2026/1002/1593746-openai-staff-fired/ ↗
[6]

Forbes Australia, Fiona Riley, "OpenAI reportedly fires 3 researchers over allegedly mishandling confidential information"

secondary named-outlet journalism
https://www.forbes.com.au/news/leadership/openai-reportedly-fires-3-researchers-over-allegedly-mishandling-confidential-information/ ↗
[7]

CNBC, Sept 28 2026, on the GPT-6.1 Astra decision

secondary named-outlet journalism
https://www.cnbc.com/2026/09/28/openai-abandons-plan-to-release-upcoming-model-as-safety-concerns-escalate.html ↗
[8]

eSecurityPlanet, Cybernews, Washington Examiner, Ynet, SiliconANGLE, Investing.com, Fox Business, NewsNation, Common Dreams

secondary syndication and derivative coverage of the WSJ chain
This citation could not be independently verified.
How links are chosen. A source is linked only when the address comes from the investigation's own retrieval or from a registry lookup (PubMed, Crossref) that matches the citation's title and year. Author lists shown as registry-verified come from the registry record, not from the report text. Citations that cannot be matched are labeled, never guessed.
This is one case on the record See the full case, browse the archive, and search every checked claim on TrueSeeker AI Open on ai.trueseeker.com →