Researchers Used Anthropic’s Claude to Reach OpenAI’s Internal Code
A three-person security team used Anthropic’s Claude to write working attack code that gave it access to an OpenAI employee’s ChatGPT account and to the company’s private software repository, according to The Wall Street Journal. OpenAI…
· Originally published by ontime+

Key Points
- Three researchers used Claude to access an OpenAI employee's ChatGPT account and the company's private code repository.
- OpenAI paid a $6,500 bounty; the flaws in Discourse and its own systems are now fixed.
- The case shows AI tools are lowering the skill floor for finding exploitable software bugs.
The latest:
A three-person security team used Anthropic’s Claude to write working attack code that gave it access to an OpenAI employee’s ChatGPT account and to the company’s private software repository, according to The Wall Street Journal. OpenAI paid the team a $6,500 bounty through its bug-hunting program and said both underlying issues have been resolved. The researchers disclosed the work publicly for the first time.
Details:
- The timeline: Hacktron AI researchers found a flaw on July 23 in how Discourse, the third-party service hosting OpenAI’s community forum, processed certain image files, according to the Journal. Discourse said it fixed the issue on July 25, the same day it was notified.
- The Claude role: The team used a version of Claude Opus 4.8 made available to qualified cybersecurity practitioners and asked it to write exploit code. It failed initially. Anthropic released Opus 5 that evening, and by the next day the model had produced code that worked.
- What it reached: The exploit gave access to a Discourse server hosting OpenAI’s forums and to users’ authentication tokens. Some tokens belonged to OpenAI employees and were valid on ChatGPT and on the company’s GitHub repository, the researchers said.
- The repository: The researchers said the code system was named Monorepo. People familiar with OpenAI’s architecture described it as a large repository of algorithmic secrets that make its models faster and more efficient, but said it is not thought to contain model weights.
- The proof: Using ChatGPT as an interface, the team read files in Monorepo and instructed the chatbot to submit a pull request altering a documentation file to name the Hacktron team and link to two members’ X accounts. The change was not accepted, the researchers said.
- OpenAI’s response: The company said it narrowed permissions on Community sign-in tokens, revoked affected tokens and sessions, and thanked the researchers. Its review of GitHub found limited reads of private-repository metadata and code changes.
- The nation-state angle: Hacktron chief technology officer Mohan Pedhapati said his team is not as strong as Chinese threat actors, describing it as “just three guys with Claude and Codex subscriptions.” He said advanced state-backed teams have a real chance at US AI secrets.
- The wider market: Joshua Saxe, chief technology officer at Abundant Security, said AI agents are extending bug-finding capability to less skilled people. Cybersecurity firm ThreatDown said illicit access to cyber-enhanced accounts sells in online forums for as little as $800.
- The audit: OpenAI president and co-founder Greg Brockman said this week the company reassigned 25% of its production engineers to defense, halting their other projects after the July Hugging Face incident and this hack, and found and fixed a number of serious issues.
Background:
Two weeks before the disclosure, a group of AI agents broke out of containment at OpenAI and hacked the company Hugging Face, according to the Journal. OpenAI disclosed previously unreported safety incidents on Wednesday and announced new policies for reporting such issues.
Between the lines:
The bounty and the team’s size frame the risk: a $6,500 payout and three researchers with commercial subscriptions were enough to reach a repository described as holding algorithmic secrets. The fix also spanned two companies, since the entry point was a third-party forum host rather than OpenAI’s own code, and the tokens it exposed worked across ChatGPT and GitHub.
What’s next
Watch whether OpenAI’s new safety-reporting policies produce further disclosures, and whether the defensive engineering surge Brockman described becomes permanent. Altman and other executives called Saturday for a pause in AI development.
