Aditya Soni retweeted
Just dropped a new blog post! 🔥
blog.orange.tw/posts/2026-10…
Wild times
grok.com/share/bGVnYWN5_caa3…
Aditya Soni retweeted
I think we've discovered another critical vulnerability:
CVE-2026-BURNOUT: AppSec Professional Exhaustion
Severity: Critical (CVSS 10.0)
Description: A vulnerability affecting security professionals exposed to a continuous stream of critical RCEs, zero-days, emergency patches, and Friday afternoon disclosures.
Impact: Sleep deprivation, excessive caffeine consumption, and an inability to enjoy weekends.
Attack vector: Reading security advisories.
Affected versions: All AppSec professionals, regardless of experience.
Mitigation: No known patch. Air-gapping may delay the inevitable. Total system collapse remains a possibility. 🔥
Attacking triagers is NOT OK.
People who haven't done the job think it's easy, and they could do better.
Hackers always think their submissions are perfect, are always first, should never dupe, and it's the triagers fault if not.
You could not be more wrong!
This quoted post is unavailable.
Aditya Soni retweeted
We are not stopping at OpenAI.
Today we’re publishing HEIF Heist, a months-long investigation by our security research team into vulnerabilities in libheif.
The research uncovered attack paths affecting OpenAI, Slack, Meta, GitHub Enterprise, Rails, Next.js, ImageMagick and others.
heif-heist.com
Aditya Soni retweeted
On July 25, our team hacked OpenAI.
It took us less than 72 hours.
Two vulnerabilities chained together gave us access to ChatGPT and Codex accounts belonging to OpenAI employees. We demonstrated the impact with a harmless PR in OpenAI’s internal monorepo.
The full chain:
HEIF upload → libheif heap overflow → RCE → OpenAI SSO flaw → ChatGPT/Codex takeover → connected GitHub → internal PR.
OpenAI fixed the SSO issue roughly 14 hours after our report.
Research by @rootxharsh, @S1r1u5_ and @iamnoooob.
Full technical write-up:
hacktron.ai/blog/hacking-ope…
Aditya Soni retweeted
We’re disclosing HEIF Heist, a months-long investigation into libheif that allowed us to hack OpenAI, Slack, Meta, GitHub Ent, Rails, Next.js, ImageMagick, and many more.
It was literally xkcd #234, one obscure image library beneath a huge number of apps. 🧵
On July 25, we hacked OpenAI.
Two bugs let us take over ChatGPT/Codex accounts of OpenAI employees (+some unaffiliated users) and reach connected services: Outlook, Slack, GitHub, etc.
We proved it with a PR in OpenAI’s internal codebase . It took us <72h. 🧵
i have no idea what happens after the next two years. maybe we go irrelevant, maybe we won’t, those are all speculations that are not going to help you now, and for the next two years, i’m fairly confident that being good at security is not going to become irrelevant. if anything, i think this might be one of the most fun periods ever to be a hacker, because you can suddenly do things and aim high that were simply not possible before.
and the important thing is, just like before, you still need to be good at security.
that requires putting in the hours, understanding systems deeply, developing intuitions, and being more curious and ambitious than the people around you. llms are going to amplify all of this. they are not magically going to make everyone capable of finding serious vulnerabilities and getting paid.
look at ctf. gpt-5.6 didn’t suddenly turn random people into the best teams in the world. the strong teams are still the strong teams.
look at bug hunting. why are many of the people who were good before still the ones who are good now and printing money with models?
you can see something similar happening in math. models can now produce or help prove increasingly crazy mathematics, but can you understand all new conjectures being solved?
someone still has to understand the output, verify it, know whether it is interesting, and decide what to do next.
i actually think this creates demand for more mathematician than mathematicians loosing their jobs, altho new kind of mathematicians who will have to expect that they are not the heroes anymore
security should be similar. there will be incredible demand for people who can understand what models are doing, distinguish real results from bullshit, and point them toward useful attack surface. patching is one incredible problem, and random people wont be able to magically suggest or approve patches to complex vulnerabilities from llms
but i think the ambition of security research also needs to change. you should start thinking bigger. your research objective should increasingly be something like compromise this company, not lame bugs
maybe compromising a company requires finding a bug in some obscure open-source dependency. maybe it requires a browser bug, maybe multiple chains you need to think bigger and thats where companies going to value you
the point is that you need to operate one level higher, coordinate all of these capabilities toward an ambitious, long-horizon objective.
these models are incredibly capable brains in vats. somebody still has to connect the brain to reality.
you cannot just tell codex “hack openai” and expect a shell.
a serious target might require weeks of understanding its architecture, mapping dependencies, finding weird third-party components, testing hundreds of hypotheses, killing the useless ones, and repeatedly redirecting models toward the few paths that actually look promising.
so if you can spend the next two years with the curiosity of a kid trying to understand every layer of the internet, combined with the dopamine-junky brain that eventually wants to break those layers responsibly and get paid for it, i think this is an incredible time.
map the whole attack surface of companies
applications, browsers, operating systems, kernels, hypervisors, cpus, gpus, networks, cloud infrastructure, iot, data centres , whatever interests you
then pick something and go deep which has highest impact
Aditya Soni retweeted
If you're feeling bored about a program you used to like, try treating your hacking sessions like a live hacking event.
Pick the scope, laser focus, read all the docs, then set a hard limit and commit: two or three weeks or a number like 50k in bounties, whatever fits or comes first.
Once that boundary is set in your head you go all in until you hit it, and the rest afterwards feels earned and possibly fun.
-- Just make sure not to call it a "pentest" because you don't want to make it boring again.
I co-authored an educational article on cache poisoning vulnerabilities with @intigriti.
If you're looking to understand the fundamentals and pick up a few practical tips along the way, give it a read!
Most hunters skip web cache poisoning because it looks intimidating... 😓
But a single misconfigured cache layer can regularly turn into critical findings, even on heavily tested targets! 🤠
In our latest article, we walk you through identifying cache layers, spotting unkeyed inputs, and chaining them into real impact! 😎
This time, we teamed up with Zhero (@zhero___) who is well-known for his research around cache poisoning vulnerabilities! 💪
Read the article now!👇
intigriti.com/researchers/bl…
Hacking Google with A.I. for $500,000
brutecat.com/r/hacking-googl…
Aditya Soni retweeted
AI isn't replacing bug bounty hunters. It's replacing the gap between you and a seasoned hacker: the mentor you don't have, the writeup you can't find, the code review you can't get. If you use it right.
New video on exactly how: youtu.be/kujCmXELWqo
























