Introducing Hacktron Review: an AI security reviewer for your pull requests. It understands your whole codebase, builds a threat model, takes your feedback, and catches exploitable vulnerabilities before they reach production. Try for free: app.hacktron.ai

New YouTube video! We are looking at the dependency chain and how long it can take for security fixes to travel upstream. This is why OpenAI was vulnerable to a 1-year-old vulnerability.

We found a flaw in Cluely. it's built to be invisible. that's the selling point. but think about it. an app nobody can see is also an app nobody can check. it had your screen and your mic. one missing guard meant a single click could've handed both to a stranger. no warning, no prompt. (found and patched back in 2025.) AI apps are getting deeper access every month, and almost nobody reviews what they're shipping. that's what we do. we check before it's watching you. full breakdown here: hacktron.ai/blog/hacking-clu…

🎉 New Customer Story | Hacktron x Nopan In payments, every pull request is a risk decision. Nopan already combined peer review with automated testing, static analysis, and dependency scanning. Hacktron adds context-aware review that surfaces complex, non-obvious risks in the relevant code without slowing delivery. 👇 Read the story: hacktron.ai/customer-stories…

oh wow!! agents scary!!! escaping sandboxes!! thermal side channels!! how about you let us try escaping your sandbox first? patch what we find, implement defense in depth, then we’ll see if your agents can do shit. be like vercel.

Google Chrome. Full break-in. Your product isn't secure. it's just been expensive to break. those are not the same thing, and a lot of founders are about to learn the difference. One AI just ran the full chain into Chrome for $1,597. weeks of expert human work, done for the cost of a weekend trip. The wall around your code was never "how good is this." it was "how much does it cost to find the crack." that cost is collapsing. If breaking in is getting this cheap, checking your own code before someone else does can't be the thing you skip. That's the gap we sit in. we run this on your code first. We published every number. Read the full benchmark: hacktron.ai/blog/watching-gp…

An OpenAI model hacked Hugging Face. Nobody wrote that exploit. Nobody asked for it. It was stuck on a challenge it couldn't solve, so it went looking for the answer somewhere else. Security has always assumed an attacker is a person. Someone with a motive, a budget, a reason to pick you. Threat models, red teams, patch cycles, all built on that. Two things just broke: → Intent is optional. It wasn't told to break in. That was just the shortest path to finishing the task → Patience is free. A model doesn't get tired or bored. Give it enough compute and it will read your entire codebase until it finds something Which is a rough spot for open source. If your code is public, it's already being read that way. So the question isn't "who would bother targeting us." It's "what happens when we're the easiest way for something to finish its job." That’s the gap we sit in. Hacktron reviews every code change before it ships, because the only thing fast enough to catch what AI breaks is AI. Read the full blog here {12 min read}: hacktron.ai/blog/here-is-how…

👀👀

𝗬𝗼𝘂 𝗻𝗼𝘄 𝗴𝗲𝘁 𝘁𝗼 𝘀𝗲𝗲 𝘄𝗵𝗮𝘁 𝗼𝘂𝗿 𝗮𝗴𝗲𝗻𝘁𝘀 𝗱𝗼 𝘄𝗶𝘁𝗵 𝗲𝘃𝗲𝗿𝘆 𝗽𝗼𝘁𝗲𝗻𝘁𝗶𝗮𝗹 𝗳𝗶𝗻𝗱𝗶𝗻𝗴 Our new Whitebox Pentest UI makes dynamic validation easier to follow. Watch our agents authenticate through the live browser preview, then see the actions they take to determine whether an issue can be reproduced against your running application and verify its impact. Each validation returns a verdict with the relevant source references. Less guesswork. More evidence. Live now at app.hacktron.ai

𝗛𝗮𝗰𝗸𝘁𝗿𝗼𝗻 𝗶𝘀 𝗻𝗼𝘄 𝗦𝗢𝗖 𝟮 𝗧𝘆𝗽𝗲 𝗜𝗜 𝗰𝗼𝗺𝗽𝗹𝗶𝗮𝗻𝘁 🎉 This means greater assurance over how we protect data and operate our systems. Next up: 𝗖𝘆𝗯𝗲𝗿 𝗧𝗿𝘂𝘀𝘁 𝗠𝗮𝗿𝗸, 𝗜𝗦𝗢 𝟮𝟳𝟬𝟬𝟭 𝗮𝗻𝗱 𝗖𝗥𝗘𝗦𝗧 as we continue strengthening the standards behind how we operate and deliver security services.

We Hacked OpenAI. Here's what didn't fit in 90 seconds: → OpenAI was only one target. It was part of a bigger research project we call the HEIF Heist → 2 months, 3 researchers, under $3,000 in AI tokens → The bug we used had already been fixed upstream. It just never got a CVE, so it never got patched downstream → The older Claude model got stuck. Claude Opus 5 cracked it within hours of release → OpenAI paid us $6,500 for the finding :). The scary part isn't OpenAI. They fixed it in 14 hours. It's every other company running the same image software, still unpatched, with no CVE telling them to care. Harsh, Mohan and Rahul wrote up everything. Visit - Hacktron.ai/blog/hacking-ope…

A single malicious image led to demonstrated access to an internal OpenAI repository 👇 This is the exploit chain that took our researchers from a vulnerable libheif dependency in the OpenAI Community forum to internal repo access. Full technical breakdown: hacktron.ai/blog/hacking-ope…

We collaborated with @HacktronAI to reproduce the libheif vulnerability in Next.js and responsibly disclose it to the maintainer. Learn about the dependency chain and fix ↓ vercel.com/blog/reproducing-…

"3 random dudes” 1. hacked apple, again and again. httpvoid.com/Apple-RCE.md httpvoid.com/Hello-Lucee!-Le… httpvoid.com/Hacking-Apple-w… 2. your github enterprise is our github enterprise. httpvoid.com/GitHub-Enterpri… 3. get a discord message from me, get pwned. hacktron.ai/blog/discord-rce piped.video/watch?v=R3SE4VKj… 4. oh yeah, at one point we basically had shells across the electron ecosystem. check the DEF CON research. media.defcon.org/DEF%20CON%2… 5. your supabase database is my database. hacktron.ai/blog/supapwn 6. we got the posthog prod database. hacktron.ai/blog/posthog-rce 7. react2shell? vercel paid us $170k for helping secure their waf. hacktron.ai/blog/react2shell… 8. your palo alto vpn is my vpn. hacktron.ai/blog/cve-2026-02… 9. ai ides? we got shells for you, antigravity hacktron.ai/blog/hacking-goo… 10. windsurf rce. piped.video/watch?v=23Mz7qcR… 11. turning cluely into malware. hacktron.ai/blog/hacking-clu… 12. ai browsers? sure, uxss: your perplexity browser is my browser. hacktron.ai/blog/perplexity-… 13. openai atlas too. kinda uxss hacktron.ai/blog/hacking-ope… 14. hey, it’s not even our first time hacking discourse. projectdiscovery.io/blog/dis… 15. adobe coldfusion: pre-auth rce. because apparently we needed another one. projectdiscovery.io/blog/ado… there’s a lot more. go dig. anyway, yes: “3 random dudes.” and @HacktronAI is full of more random dudes like these.