← DOOMRADAR
Cyber & digital services55 / 100 · Doom score

Researchers say Claude-assisted hackers accessed OpenAI employee accounts and internal code

Researchers say attackers chained vulnerabilities to compromise multiple OpenAI employee ChatGPT accounts and access internal repositories. The reported access could have exposed connected services, but the material does not establish broader customer impact.

By DoomRadar · Published on DoomRadar . Updated .

How the effects could reach youConditional effectsConditional impact diagram. Reported development: Researchers say Claude-assisted hackers accessed OpenAI employee accounts and internal code. digital: Organizations using connected coding or collaboration services may need to review credentials and integrations. Only if: The reported account compromise must be confirmed and the relevant integrations must have been reachable. These are possible effects, not probabilities or a forecast.
A possible pathway, conditional on the factors shown.Reported basis: [1][2][4][3]

What happened

Hacktron says attackers chained a heap-overflow vulnerability with an SSO misconfiguration to compromise multiple OpenAI employees’ ChatGPT accounts on July 25, 2026. [1]

References for this detail (1)
  • Hacking OpenAIhacktron.ai · Recorded source date: Sep 18, 2026, 4:02 AM UTC

Hacktron says the attackers used an employee’s Codex account to open pull request 1186742 in OpenAI’s internal repository as proof of access. [1]

References for this detail (1)
  • Hacking OpenAIhacktron.ai · Recorded source date: Sep 18, 2026, 4:02 AM UTC

Context from the sources

Hacktron says the affected accounts could have provided access to services connected to ChatGPT and Codex, including other connectors, though the excerpt does not establish that sensitive data was taken. [1]

Explore the sources and reporting timeline

4 source links · 4 domains

These counts describe the references, not independent confirmations. Different outlets can repeat the same original report.

Source timeline

Oldest to newest among the available source dates, not a chronology of the incident. Article publication dates come from the source; other recorded dates may reflect when a link was found.

  1. Recorded source date: Sep 18, 2026, 4:02 AM UTC[1] Hacking OpenAIhacktron.aiReferenced for: detail 1, detail 2
  2. Recorded source date: Sep 18, 2026, 7:46 AM UTC[4] Anthropic's AI security tool hacked OpenAI systems and accessed employee credentials: Here's what happenedbusinesstoday.inReferenced for: detail 4
  3. Recorded source date: Sep 18, 2026, 11:31 AM UTC[3] OpenAI 'ethically hacked' with help of Anthropic's Claude chatbotaol.co.uk
  4. Recorded source date: Sep 18, 2026, 12:17 PM UTC[2] 3 guys using Anthropic's Claude hacked into OpenAI and accessed its source code for $6,500 rewardfortune.comReferenced for: detail 3

What this could mean for you

Digital services

Organizations using connected coding or collaboration services may need to review credentials and integrations.

Compromised employee accounts can provide an attacker with access to linked services and repositories.

Reported basis: [1][4] · The possible effect is interpretation.

Depends on: The reported account compromise must be confirmed and the relevant integrations must have been reachable.

Possible consequences, not a forecast. Their relevance depends on your location and the conditions above.

For your country

Choose a country to check how this event could affect you.

What changes the outlook

Risk increases if…

Evidence that production systems, customer data or additional connected services were accessed.

Confirmation that compromised credentials remained valid after the reported intrusion.

Pressure eases if…

Independent confirmation that access was limited to a test repository and affected credentials were promptly revoked.

Still unclear

Whether OpenAI confirmed the incident and which accounts, repositories or connectors were actually accessed.

Whether any customer data, secrets or production systems were accessed or changed.

Market implications

Market impact

Loading market analysis...
Sources (4)

References for the reported details. Separate links do not necessarily mean independent confirmation.

[1] Hacking OpenAI ↗hacktron.ai · Recorded source date: Sep 18, 2026, 4:02 AM UTC
Available excerpt
A heap overflow and SSO misconfiguration to compromise OpenAI internal repositories On July 25, 2026, we chained two critical vulnerabilities to compromise multiple OpenAI employees’…
A short excerpt from our source record; open the original for the full article.

First tracked by DoomRadar: . AI-assisted analysis · . Based on linked headlines and available excerpts. Methodology · Report an error.