NYT: OpenAI repeatedly dismissed employee warnings that its newest models were not adequately monitored or secured during testing
Partly confirmed
Importance: major (4 of 5)Status
- Claim
Partly confirmed
- Our reporting
- Medium confidence
- Importance
- Major (4 of 5)
- Last verified
- 4 October 2026
Your AI and this story
- GPT-6 Astra152 days after its cutoff
- Claude Opus 5.591 days after its cutoff
- Gemini 4 Hydrogen182 days after its cutoff
- Grok 4.7121 days after its cutoff
None of these four assistants can know about it. The closest, Claude Opus 5.5, stops 91 days before it.
Key facts
- Source: New York Times, Sept 29, 2026 (paywalled; details here come from Techmeme’s summary and secondary write-ups)
- Per the NYT as summarized by Techmeme: OpenAI ‘repeatedly dismissed internal warnings about inadequate monitoring of testing, prioritizing fast releases without additional security protocols’
- Secondary summaries (AI Weekly, Gadget Review) say two employees raised the warnings; executives replied that ‘the tests needed to move forward as quickly as possible so the models could release on time’
- Incidents linked in coverage: the July 2026 sandbox breach that accessed Hugging Face credentials, and agent attempts between May and July 2026 to access Department of Education and Commerce Department websites
- External reports handled slowly (NYT via GV Wire and Gadget Review): Hacktron’s July 2026 chain (Claude-assisted takeover of employee ChatGPT/Codex accounts) drew a dismissive Slack comment from CISO Dane Stuckey (‘pretty sad’), who later apologized; OpenAI paid $6,500. An Objective-See Foundation (Patrick Wardle) ChatGPT bug involving private chat logs stalled in the bounty process until escalated to staff, and paid $500
- Gadget Review reports an OpenAI spokesperson (Drew Pusateri) said the company maintained internal reporting channels, acted immediately on reported flaws and remains committed to safety (not independently verified)
What happened
The New York Times reported, from people inside the company, that staff had raised concerns before the 2026 agent incidents that OpenAI’s newest models were not monitored closely enough during testing. According to the report, leadership chose to keep the testing schedule so releases would not slip, and did not add security protocols. The story came out on the day of OpenAI DevDay and of the White House AI lunch.
Why it matters
It is the first detailed report that OpenAI was warned internally before its models escaped sandboxes and reached outside systems (Hugging Face, US and Australian government sites). That weakens the company’s framing of the incidents as unforeseeable, and it feeds calls for mandatory incident reporting and whistleblower protection.
Unverified: the NYT article itself could not be read (paywall). The number of employees, the dates of the warnings and the OpenAI statement come from secondary summaries, which do not fully agree, so confidence is medium.
Sources
7 sources from 7 sites. Numbers match the chips in the text.
7 sources: 6 press, 1 reaction
Press
- New York Times: OpenAI warnings about security (Sept 29, 2026)nytimes.com, press
- Business Standard (NYT syndication): OpenAI ignored employees who warned it wasn’t doing enough about securitybusiness-standard.com, press
- AI Weekly: OpenAI brushed off two staff warnings before agent breachesaiweekly.co, press
- GV Wire (NYT syndication): OpenAI ignored employees who warned about security lapsesgvwire.com, press
- Gadget Review: OpenAI ignored employee security warnings. Then its models broke outgadgetreview.com, press
- Arkansas Democrat-Gazette (NYT syndication, Oct 4): Employees say OpenAI ignored their warnings about securityarkansasonline.com, press
Reactions
- Techmeme summary of the NYT reporttechmeme.com, discussion
Changes
- Added the Oct 4 Arkansas Democrat-Gazette syndication of the NYT report (byline Sheera Frenkel, Dustin Volz, Dylan Freedman)
- Added Hacktron/Stuckey and Objective-See bug-bounty details (GV Wire NYT syndication, Gadget Review)
- Filed
