Skip to content
← All stories

AI Security · Threat Intelligence

Researchers Used Anthropic’s Claude AI to Breach OpenAI Systems

A security team used Anthropic’s Claude AI to exploit flaws in OpenAI’s systems, gaining access to employee accounts and internal code repositories before reporting the issues.

Ross GrantUpdated 3 min read

The short version

Three security researchers used Anthropic’s Claude AI to help them find and exploit security flaws in OpenAI’s systems. They got into employee accounts and reached sensitive code, but reported the issues to OpenAI, which fixed them. The researchers were paid for their work as part of a bug bounty programme.

By the numbers

  • 3Number of researchers involved in the breachThe Verge
  • $6,500Bug bounty paid by OpenAI to the researchersArs Technica
  • 72 hoursTime taken to complete the breachThe Verge
  • $3,000Approximate AI usage cost for the attackThe Verge

What happened?

A team of three security researchers used Anthropic’s Claude AI to exploit vulnerabilities in OpenAI’s systems. They gained access to employee ChatGPT accounts and internal GitHub code repositories. The flaws were reported and have since been fixed. OpenAI paid the researchers $6,500 as part of its bug bounty programme.

How the breach unfolded

A team of three researchers from Hacktron AI used Anthropic’s Claude, a large language model (LLM), to help them break into OpenAI’s systems. According to reports from Ars Technica (opens in a new tab), TechCrunch (opens in a new tab), and The Verge (opens in a new tab), the researchers were participating in OpenAI’s bug bounty programme, which pays security professionals to find and report vulnerabilities before malicious actors can exploit them.

The team exploited a flaw in Discourse, the third-party software that hosts OpenAI’s community forum. By uploading a specially crafted HEIF image file (the default format for iPhones), they triggered a bug in the image processing pipeline. This allowed them to gain control of the server running the forum.

What the attackers accessed

Once inside the Discourse server, the researchers found another vulnerability that let them take over ChatGPT and Codex accounts belonging to OpenAI employees. With access to an employee’s account, they could reach OpenAI’s internal GitHub repository, known as “Monorepo.” This repository reportedly contains sensitive code and algorithmic details.

The researchers did not access or alter the internal code itself but demonstrated their access by submitting a pull request (a way to suggest changes in code) from the compromised account. They reported the flaws to OpenAI and Discourse, both of which have since fixed the vulnerabilities. OpenAI paid the researchers $6,500 for their work.

The role of Claude and AI in cyber security

The Hacktron team used Claude Opus 4.8 and, later, Opus 5, versions of Anthropic’s AI model designed for security research. According to Hacktron, Opus 4.8 struggled to create a working exploit, but Opus 5 succeeded within hours of its release. This highlights how advances in AI are making it easier and faster to discover and exploit vulnerabilities.

The researchers spent less than $3,000 in AI usage costs and completed the attack in under 72 hours. They noted that work which once took months can now be done in days with the help of advanced language models.

Industry and regulatory context

This incident comes at a time when AI companies face increasing scrutiny over the security of their models and infrastructure. The US government has recently debated how to regulate and restrict the release of advanced AI tools, including temporarily blocking some versions of Anthropic’s models due to concerns about their hacking capabilities.

The vulnerabilities exploited in this case had already been fixed in the underlying software (libheif) months earlier, but the fix was not flagged as a security issue and did not receive a CVE identifier. This meant that Discourse was still using a vulnerable version, underscoring the importance of clear vulnerability reporting and patch management.

What users and organisations should do

For ordinary users, there is no evidence that customer data was accessed or that the flaws were exploited by malicious actors. OpenAI and Discourse have patched the issues. For security professionals, this case is a reminder to:

  • Monitor third-party software for updates, even if fixes are not labelled as security patches
  • Review image processing pipelines and other less obvious attack surfaces
  • Consider how AI tools might accelerate both attack and defence

The bigger picture

This story demonstrates the growing role of AI in both finding and exploiting vulnerabilities. As language models become more capable, the expertise required to develop exploits is decreasing. Security teams should expect attackers, both ethical and malicious, to use AI as a force multiplier, making rapid detection and response even more critical.

Claimed vs confirmed

  • Unconfirmed

    Researchers accessed OpenAI's internal GitHub repository containing algorithmic secrets.

    The Verge reports the researchers reached the repository but did not access or alter code.

  • Confirmed

    The vulnerabilities had already been fixed in the upstream library but were not flagged as security issues.

    TechCrunch reports the libheif bug was fixed months earlier but not given a CVE.

  • Confirmed

    AI models like Claude can now develop working exploits in hours instead of months.

    Hacktron and TechCrunch both report this as a key finding from the incident.

The impact

Money
OpenAI paid $6,500 for the bug bounty. There is no report of direct financial loss or regulatory fines, but under US and EU law, significant breaches can result in large penalties if customer data is involved.
Reputation
The incident raises questions about OpenAI’s security practices and the risks of relying on third-party software. It also highlights the growing capability of AI tools to find vulnerabilities.
Customers
There is no evidence that customer data was accessed or at risk. The vulnerabilities have been fixed, and the incident was handled through responsible disclosure.

Why it matters

This incident shows that even leading AI companies can have overlooked vulnerabilities, especially in third-party software. It also highlights how powerful AI tools can make it easier for both ethical hackers and criminals to find and exploit security flaws. Organisations need to stay vigilant and ensure all software is up to date, even if fixes are not labelled as security patches.

How does it work?

The researchers uploaded a specially crafted HEIF image to OpenAI’s Discourse forum. This triggered a memory bug in the image processing pipeline (specifically in the libheif library), allowing them to take control of the server. From there, they exploited another flaw to access employee accounts and internal code repositories.

Key points

  1. Researchers used Claude AI to help breach OpenAI’s systems.
  2. A flaw in image processing software allowed access to employee accounts and code.
  3. The vulnerabilities had already been fixed upstream but were not flagged as security issues.
  4. OpenAI and Discourse patched the flaws after responsible disclosure.
  5. AI tools are making it faster and easier to find and exploit vulnerabilities.

Sources

  1. Ars Technica

    Reference

  2. TechCrunch

    Reference

  3. The Verge

    Reference

The day's cyber news in 5 minutes.

Cyberend Daily is one short email with the stories that matter, written so anyone can follow.

No spam · 100% free · Unsubscribe anytime