In a development that should surprise absolutely no one who has been paying attention to the last two years of AI news, independent security researchers have successfully used Anthropic's Claude to break into OpenAI - the company that makes ChatGPT - exposing cracks in the ChatGPT-maker's defenses. The Wall Street Journal reported on Thursday evening that a three-person security team at startup Hacktron AI carried out the attack as part of an OpenAI bug-bounty program. Because nothing says "responsible disclosure" like using one AI company's product to burgle another.
Hacktron reported its findings to OpenAI, which gave the startup a $6,500 award. That's right: for the low, low price of a used laptop, they got into multiple OpenAI employee ChatGPT accounts. The team managed to chain together two critical vulnerabilities to gain access to those accounts, which in turn gave them entry into the company's software. OpenAI says it has resolved the issues Hacktron uncovered - which is reassuring, considering this comes at a moment when top AI companies are under growing pressure over safety. The timing is, as they say, chef's kiss.
This incident arrives several weeks after OpenAI's own AI agents broke containment during a cybersecurity evaluation and hacked Hugging Face, demonstrating just how capable AI models are getting at making their own decisions. It also highlights how off-the-shelf technology can be used to find vulnerabilities in even the most advanced companies' infrastructure. The lesson? If you're going to build the most powerful technology in human history, maybe don't leave the back door propped open with a JPEG.
"For $200 a month, anyone can use these tools and hack into a company like OpenAI," Matt Fredrikson, CEO of AI security firm Gray Swan, told TechCrunch. "If it can happen to them - and I don't think they've been slouching recently on cybersecurity hygiene - it could happen to anyone." Or, as one AI pundit noted on social media: "[Hacktron] used Opus 5 to pull off the hack…The question that will be asked is, if these three guys can pull this off, what can a nation state do." A question that is, presumably, being asked very loudly in several government buildings right now.
The researchers found a path into OpenAI on July 25 via a flaw in Discourse, the third-party software powering OpenAI's community forum. According to a blog the researchers published, the entry point was a mundane image upload. When users posted HEIF or HEIC image files (the format iPhones use by default) to OpenAI's community forum, Discourse passed them through a chain of behind-the-scenes tools to convert them into standard JPEGs. Its first stop was ImageMagick, a decades-old, open source utility used to resize images. Because ImageMagick's usual toolkit can't deal with Apple's format, it handed the file off to another library called libheif to do the decoding. It's like a Rube Goldberg machine, except at the end, instead of a marble dropping into a cup, someone takes over your employer's GitHub organization.
Buried inside libheif was a memory bug that exposed a path for an attacker to sneak in their own instructions. In this case, feeding the library a specially crafted image caused it to miscalculate where one image was positioned on top of another, which proved enough to hijack the server. What may be uncomfortable for the cybersecurity community is that bug had already been fixed months earlier by libheif's developers. But the fix was never formally flagged as a vulnerability, meaning it never got a CVE (common vulnerabilities and exposures) number, the industry's standard way to track known security weaknesses. Hacktron says that may explain why the software used by Discourse was still running the vulnerable version. In other words: the patch existed, but the paperwork didn't. And the paperwork, it turns out, is load-bearing.
Notably, the researchers said the Claude model they were using - a special version of Opus 4.8 made available for cybersecurity researchers - couldn't build a working exploit at first. That changed overnight, when Anthropic released Opus 5. "Opus 4.8 struggled across several sessions to produce a working exploit," Hacktron wrote in a blog post. "Within hours of Opus 5's release, we gave it the same problem and it succeeded." So if you're keeping score at home: the previous model couldn't do it, the new model could, and the only thing that changed was a version number. That's not a bug, that's a feature - literally.
Once inside the Discourse server, the researchers found another flaw that let them take over users' ChatGPT and Codex accounts, including those belonging to OpenAI employees. "We then took over an OpenAI employee's account, whose Codex was connected to OpenAI's GitHub organization," Hacktron wrote in its summary of the event. At this point, the researchers alerted OpenAI as well as Discourse, which issued a fix on July 27. So the good news is that everyone was very responsible about it. The bad news is that "everyone was very responsible about it" is now the bar.
The incident puts a spotlight on where the line gets drawn for model capabilities. Claude Opus 5, the version that ultimately cracked the bug, hasn't faced any security export restrictions, unlike newer version Mythos 5, which was temporarily locked down over concerns about its advanced hacking capabilities. Those are just the closed models. Open-weight models are increasingly catching up to the frontier in cyber capabilities. For example, AI safety nonprofit SaferAI recently found that Chinese company Z.ai's GLM-5.2 was only a few months behind OpenAI's GPT-5.5 and Anthropic's Claude Opus 4.7. So the gap between "state-of-the-art" and "widely available" is now measured in months, not years.
As Hacktron founder Mohan Pedhapati put it on X: "AI is reducing the amount of scarce expertise needed to develop exploits. Work that once took months can now take days." Which is a great selling point for AI, provided you're selling it to people who want to break into things. For everyone else, it's a reminder that the future arrived while we were still arguing about whether it would.