OpenAI Fired Three Safety Researchers Over a Leak It Still Won’t Explain

OpenAI fired three employees after an internal investigation found they shared sensitive company information with an outside AI safety evaluation group. The company hasn't said what was shared, who received it, or why.

Get a summary in:
Empty office chair reflected in a glass office building, representing an employee departure
Follow Teck Hustlers on Google
Add Teck Hustlers as a preferred source to see more of our stories in Google Top Stories.
Add as preferred source on Google
AA

Admin Alex
Writer
MA

M.Ali
Fact-Checker

Published: October 2, 2026 · Last updated: October 2, 2026

TL;DR: OpenAI fired three employees this week after an internal investigation found they shared sensitive company information with an outside AI safety evaluation group. The company hasn’t said what was shared, who received it, or why. That silence is the story.

A golden padlock sitting on top of a computer keyboard, symbolizing confidential company information

Three people lost their jobs at OpenAI this week, and the company is telling almost nobody why.

According to a report first surfaced by the Wall Street Journal and matched since by several outlets, OpenAI dismissed the three employees after an internal investigation concluded they had passed along sensitive or proprietary company information to an external AI safety evaluation organization. OpenAI has not named the employees. It has not named the outside group. It has not described what information actually moved.

That’s an unusual amount of silence for a company that spent much of the last two years trying to convince the public it takes outside scrutiny seriously.

OpenAI has built relationships with independent evaluators before, sometimes publicly, sometimes through narrower arrangements where a research group gets limited access to a model ahead of release in exchange for running safety tests. Those arrangements typically come with nondisclosure terms about what the evaluator sees and how findings get reported back. If someone broke the terms of that kind of access agreement, rather than simply blowing a whistle, that’s a contract and trust problem more than a courage-under-pressure story. If instead someone flagged something they believed the public needed to know and OpenAI treated that as a firing offense, that’s a very different story, and a worse one for the company.

OpenAI isn’t saying which version happened.

The timing matters too. The firings land in a year where OpenAI has already dealt with high-profile departures from safety-focused teams, congressional attention on how frontier labs handle internal dissent, and a running public argument about whether AI companies can police themselves at all. Every time a safety-adjacent employee leaves under unclear circumstances, it reopens that argument, whether or not this particular case has anything to do with model safety research itself.

It’s also worth separating two different kinds of “leak” that get flattened into one word in headlines like this. Leaking a user’s private data is a privacy violation. Leaking a company’s unreleased roadmap to a competitor is corporate espionage. Sharing information with an independent safety evaluator, even without authorization, sits somewhere else entirely, closer to how journalism and research oversight are supposed to work in other industries. OpenAI’s statement, such as it is, doesn’t tell us which bucket this falls into.

Until OpenAI says more, or until the fired employees or the evaluator they allegedly contacted says more, this stays a rumor with real consequences attached. Three careers ended. The explanation didn’t.

Compare this to how other industries handle outside review. Financial auditors, clinical trial reviewers, even restaurant health inspectors operate under rules that spell out exactly what information can flow where, and violating those rules has clear, published consequences that everyone involved agreed to in advance. AI safety evaluation has no equivalent rulebook yet. Every lab writes its own terms for who gets to look inside the house and what they’re allowed to say about what they saw, and those terms rarely get published anywhere a reporter or a researcher can check them. That gap is exactly why a story this vague can spread this fast. Nobody outside OpenAI has the baseline information needed to judge whether three people broke a reasonable rule or got punished for doing their job too well.

There’s a version of this story where OpenAI comes out in a week with a tight, specific explanation that makes the firings look obviously justified. There’s another version where it never explains itself at all, and the vagueness becomes the headline that sticks. Companies usually get to pick which version happens by choosing how fast and how clearly they talk. OpenAI, so far, has chosen neither speed nor clarity.

Related: ChatGPT Will Now Dress You Before You Buy Anything and AMD Just Paid $8.2 Billion for Fei-Fei Li’s Lab, and Made Her Chief Scientist.

Bottom Line: A company that wants credit for welcoming outside scrutiny doesn’t get to fire people over an unnamed leak to an unnamed safety group and call that transparency. OpenAI owes a fuller account here, and the longer it waits, the worse the eventual explanation will have to be.

Follow Teck Hustlers: Facebook · X · Instagram · LinkedIn · TikTok · Pinterest

Follow Teck Hustlers on Google
Add Teck Hustlers as a preferred source to see more of our stories in Google Top Stories.
Add as preferred source on Google