Aditya Soni (@hetroublehacker) header
Aditya Soni (@hetroublehacker) profile picture

~ Your friendly neighbourhood hacker ¯\_(ツ)_/¯

Joined December 2011
Photo by Aditya Soni (@hetroublehacker)Photo by Aditya Soni (@hetroublehacker)Photo by Aditya Soni (@hetroublehacker)Photo by Aditya Soni (@hetroublehacker)Photo by Aditya Soni (@hetroublehacker)Photo by Aditya Soni (@hetroublehacker)Photo by Aditya Soni (@hetroublehacker)Photo by Aditya Soni (@hetroublehacker)Photo by Aditya Soni (@hetroublehacker)Photo by Aditya Soni (@hetroublehacker)
Aditya Soni retweeted
My @offensive_con Tokyo talk is now live! Watch how we bypassed @telegram’s server-side sticker validation… multiple times! And stay tuned for the full research with @the_st0rm at @BlackHatEvents Europe! youtu.be/WXaJIZBLUkw
2
39
1
187
7,610
Aditya Soni retweeted
Replying to @pedrib1337
(using AI to dictate and organize) yes, truth oracle = RAG system. I have multiple truth oracles, all following the same design principles. Let's say the model flags a potential deserialization vuln in a Ruby app. The oracle retrieves the most relevant information, e.g. Ruby versions v/s working deserialization gadgets, universal gadgets (if applicable), exact exploitation chains, prerequisites, caveats, etc. The goal is to minimize the path of thinking/reasoning for the model and offload the search/retrieval responsibility to the oracle. Yes, the model still reasons (and this is where the intelligence is), but offloading a lot of this process makes it v efficient and fast. This is especially relevant because I often work in air-gapped envs (no network access, other than the model calls being made). The oracle stays local and gets updated v frequently, so if a new exploit drops (e.g. a PoC of php2shell becomes available, or any new development happens), the oracle gets updated, and my harness + model in the air-gapped env can query all the latest available info. The setup is fairly simple: - Multiple specialized oracles for different vuln classes, languages, frameworks, and behaviors. - Knowledge indexed from research papers, CVEs, PoCs, writeups, patches, vulnerable code patterns etc. - Context-aware retrieval based on code, versions, observed behaviors, and prerequisites. Main alpha is ranking/retrieval algos and how to fetch the absolute best possible result. - Behavioral mapping to identify whether similar behavior has led to exploitation previously. - Attack-chain mapping to identify possible escalation paths. - Minimal, highly relevant context returned to the model instead of dumping entire documents. - Continuous updates, with periodic syncs to air-gapped envs. - Feedback loops from validated findings, failed hypotheses, and previous engagements. This gives a massive edge in both blackbox/whitebox engagements. Especially in blackbox, where the number of things to try is practically unlimited, and agents suck at deciding what to try next. The harness encounters a behavior → queries the oracle → retrieves relevant prior research → the model reasons about applicability → validates it. We are not replacing the model's intelligence. we re just making it spend its reasoning budget on the actual problem rather than recalling obscure techniques or searching through irrelevant possibilities. The result is fewer tokens, faster research, and potentially more valid findings. I have a full system that has proven to work for me and can beat the majority of systems out there. Might make the entire setup public if I get the bandwidth.
4
3
1
35
3,255
I built HexBrain: every publicly disclosed HackerOne report on one interactive map. 15,000+ reports by vulnerability class, weakness and program Full write-ups: how each bug was actually found 405,000+ CVEs, exploited ones in red Bypass and payload libraries It's free and still early, so tell me what breaks or what's missing. hexbrainai.com #bugbounty #infosec #bugbountytips
76
182
12
1,043
42,995
Aditya Soni retweeted
HOLY MOLY CRYPTO
1
1
3
735
Aditya Soni retweeted
Triaging experience at @Bugcrowd is extremely bad, even the valid demonstrated findings with POC and high - critical impacts are being marked N/A with templated comments.
38
21
10
308
29,785
Aditya Soni retweeted
Everyday is zero-day these days
4,087
5,921
1,104
73,281
8,482,055
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. 🔥
56
386
39
1,866
108,781
Aditya Soni retweeted
what a day for the security industry
20
49
2
533
11,049
Aditya Soni retweeted
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.
15
10
2
92
10,704
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
15
104
16
813
49,347
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…
84
386
99
3,446
403,329
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. 🧵
48
427
66
3,225
562,401
Aditya Soni retweeted
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. 🧵
353
1,378
547
11,770
2,828,136
Aditya Soni retweeted
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
9
23
5
198
12,740
Aditya Soni retweeted
It is your reminder to not buy bug bounty courses in 2026.
4
5
2
104
21,428
Aditya Soni retweeted
Pleased to publish a browser-related research paper (w/@inzo____) titled: One trigram at a time: XSLeak via Universal CSS Injection and DoS in Opera (GX) The title speaks for itself. Enjoy the read! zhero-web-sec.github.io/rese…
5
62
4
263
28,287
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.
1
15
2
163
10,647