Skip to content

Leadership Reports disagree4 publishers 3 min read Published Updated

OpenAI paid $6,500 for a three-bug chain that reached its private monorepo

Hacktron AI chained a Discourse image-library flaw to a weakness in OpenAI's single sign-on and into the Codex environment in under 72 hours, after swapping Claude Opus 4.8 for Opus 5 to get a working exploit.

The Board Room · Leadership desk

Send a correction

What happened

  • Hacktron AI reported a three-stage chain to OpenAI's Bugcrowd program on July 25, 2026, and collected a $6,500 bounty for it.
  • From code execution on a Discourse forum, the team pivoted through a flaw in OpenAI's single sign-on, took over an employee's ChatGPT account and reached the Codex environment wired to OpenAI's GitHub organization.
  • Inside the openai/openai monorepo the researchers opened a harmless pull request to prove they were there, and stopped short of examining sensitive source code.

Why it matters

  • What it limits constraint A per-report price set when memory-corruption work took weeks stops rationing submissions once the same work takes hours.
  • Who's exposed exposure OpenAI's private code was reachable through a third-party forum's image library. That puts the patch discipline of community software vendors on the same path as the monorepo.
  • What it sets up precedent A model released one day before the report changed the outcome. For security teams that makes re-testing what an attacker can build a per-release item.

Hacktron's team found Claude Opus 4.8 unreliable for the exploit work [16]. Opus 5, released on July 24, produced a working ARM64 exploit within hours, and the team adapted it for x86-64 and jemalloc environments [17]. Memory-corruption exploit development is specialist work that has historically taken skilled humans weeks [8]. The published account does not say how much of the chain the model drove, how much the team did, or how large the team was. Before reading the Opus 5 result as the end of a talent constraint, note who was at the keyboard: researchers affiliated with the security startup Hacktron AI [6].

OpenAI paid $6,500 for a report that ended with a pull request inside openai/openai [1][4]. Spread across the under-72-hour window, that is about $2,170 per calendar day [14][7]. For a program owner the constraint sits elsewhere. Coinbase has warned that bug reports could triple in the near future as AI floods disclosure programs with noise [12]. A program pays per valid report and pays humans to read the invalid ones. The payout schedule sets only the first of those two prices.

The volume evidence sits alongside that single chain. Chainalysis reported this week that attackers are posting malware instructions to public blockchains 440% more often than a year ago, with daily malicious onchain writes climbing from 2.06 to 11.1 [9], a ratio of roughly 5.4 to one [15]. Those figures count malware staging on public ledgers, a different thing from intrusions at frontier labs. Chainalysis tied the jump to mid-2025, when open-weight Chinese models launched without meaningful guardrails against writing malicious code, and called the technique blockchain dead drops [10]. By the second quarter of 2026, state-linked operators from North Korea and Iran accounted for roughly two-thirds of new activity and about half the total [11]. Researchers tracking North Korea's Kimsuky found Ollama, GPT4All and Msty installed on the group's infrastructure alongside AI-generated phishing decoys [13].

The timeline explains part of why the price looks low. OpenAI fixed the vulnerability the same day it was reported, and Discourse published its advisory on July 28 with a CVSS severity of 8.8 [5]. The episode became public on Sept. 17, when the Wall Street Journal reported it [18], 54 days after the report landed [19]. OpenAI set the payout while it and Hacktron were the only parties who could see the chain.

The decision in front of a program owner this quarter is narrow: a rate card that separates a chained path to source access from a single finding, and enough triage capacity for the volume Coinbase describes [12]. The longer question is whether a payout sized for scarce human exploit work still clears a market where a three-stage chain into a frontier lab takes under three days [7]. Opus 4.8 could not do that task, and Opus 5, one release later, could [16][17].

What to watch

  • Whether OpenAI or comparable programs revise their rate cards for chained access after the Bugcrowd report becomes widely known.
  • Whether Coinbase's projection of tripled report volume shows up in published disclosure-program statistics.
  • Whether a later published chain comes from a team without prior exploit-development background. That would test the talent question directly.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence60
Adoption
Not scored
Hype gap+30
Incentives65
Confidence55

Perspective Coverage

4 publishers
Builder
Builder 30%
Operator
Operator 41%
Investor
Investor 29%
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Hacktron AI reported the OpenAI chain through Bugcrowd on July 25, 2026, and collected a $6,500 bounty.

    Reported Supported Source: news.bitcoin.comView cited source
  2. [2]

    A vulnerable libheif library inside Discourse, the forum software, allowed remote code execution on the forum itself.

    Reported SupportedView cited source
  3. [3]

    From the forum the team pivoted through a flaw in OpenAI's single sign-on flow, took over an employee's ChatGPT account, and reached the Codex environment wired to OpenAI's GitHub organization.

    Reported SupportedView cited source
  4. [4]

    That access opened the openai/openai monorepo, where the researchers opened a harmless pull request to prove they were inside and stopped short of examining sensitive source code.

    Reported SupportedView cited source
  5. [5]

    The vulnerability was fixed the same day it was reported, and Discourse published its advisory on July 28 with a CVSS severity of 8.8.

    Reported SupportedView cited source
  6. [6]

    The researchers were affiliated with the security startup Hacktron AI.

    Reported SupportedView cited source
  7. [7]

    The whole job took under 72 hours.

    Reported SupportedView cited source
  8. [8]

    Memory-corruption exploit development is specialist work that has historically taken skilled humans weeks.

    Reported SupportedView cited source
  9. [9]

    Chainalysis reported this week that attackers are posting malware instructions to public blockchains 440% more often than a year ago, with daily malicious onchain writes climbing from 2.06 to 11.1.

    Reported Supported Source: Chainalysis, via news.bitcoin.comView cited source
  10. [10]

    Chainalysis tied the jump to mid-2025, when open-weight Chinese models launched without meaningful guardrails against writing malicious code, and called the technique blockchain dead drops.

    Reported Supported Source: Chainalysis, via news.bitcoin.comView cited source
  11. [11]

    By the second quarter of 2026, state-linked operators from North Korea and Iran accounted for roughly two-thirds of new activity and about half the total.

    Reported Supported Source: Chainalysis, via news.bitcoin.comView cited source
  12. [12]

    Coinbase recently warned that bug reports could triple in the near future as AI floods disclosure programs with noise.

    Reported Supported Source: Coinbase, via news.bitcoin.comView cited source
  13. [13]

    Researchers tracking North Korea's Kimsuky found local LLM platforms including Ollama, GPT4All and Msty installed on the group's infrastructure alongside AI-generated phishing decoys aimed at virtual asset and financial investment targets.

    Reported SupportedView cited source
  14. [14]

    A $6,500 bounty spread across a job of under three days is about $2,170 per calendar day.

    Derived Supported
  15. [15]

    Daily malicious onchain writes of 11.1 against 2.06 is a ratio of about 5.4 to one.

    Derived Supported
  16. [16]

    The team first tried Claude Opus 4.8 but found it unreliable for the task.

    Reported ContestedView cited source
  17. [17]

    Claude Opus 5, released July 24, produced a working ARM64 exploit within hours, which the team then adapted for x86-64 and jemalloc environments.

    Reported ContestedView cited source
  18. [18]

    The episode only became public on Sept. 17, when the Wall Street Journal reported it.

    Reported ContestedView cited source
  19. [19]

    54 days passed between the July 25, 2026 report and the Sept. 17 public account.

    Derived Contested

Sources

4 independent publishers whose own reporting we read for this story.

  1. businessinsider.com

    1 article · September 17, 2026

    This tiny cybersecurity startup managed to hack OpenAI using Claude, and won a $6,500 bounty
  2. cbsnews.com

    1 article · September 18, 2026

    AI security experts say they used Claude to hack ChatGPT - CBS News
  3. news.bitcoin.com

    1 article · September 18, 2026

    White Hats Used Anthropic's Claude to Break Into OpenAI in 72 Hours
  4. theguardian.com

    2 articles · September 18, 2026

    OpenAI ‘ethically hacked’ with help of Anthropic’s Claude chatbot

Topics and entities