
segfaulting through life & learning security 📉. I also like websec, softwaresec and static analysis, prev: @snyksec,@mwrinfosecurity, @notsosecure
@gitlab
Joined January 2013
- Tweets2.3K
- Following664
- Followers612
- Likes5.3K
Sam Sanoop retweeted
The RCE for nginx needs 128GB of HTTP/2 traffic to trigger and specific CPU instructions to be exploitable
I hope I saved you some time.
Sam Sanoop retweeted
hello we are an agentic security research company here's a new vuln for [popular application] we found with our harness that we are irresponsibly disclosing on twitter because its good for marketing PLEASE BUY OUR PRODUCT
Sam Sanoop retweeted
realizing all the hard shit you accomplished on your resume pre 2026 is just a prompt now
We managed to find a way to backdoor the next release of OpenAI Codex 🔥
This is the best exploit chain I’ve ever witnessed
depi.security/blog/20261111-…
Sam Sanoop retweeted
Finding CVEs is now the new 3D printing for infosec: There's no effort, nobody wants them, and we all have to pretend to be impressed.
Sam Sanoop retweeted
Today @_rybaz and I are publicly releasing all the materials for our Introduction to Harness Engineering for Vulnerability Research training we gave at @unpromptedconf last week.
Our goal was to teach the concepts we've been using to do much deeper security research and make both vulnerability analysis and red team engagements far more impactful.
The workshop can be found here: grahamhelton.github.io/harne…
The slides can be found here: grahamhelton.com/talks/2026-…
Better late than never. I published my writeup on Pwn2Own Berlin May 2026 on LMStudio RCE chain (fixed long time ago) blog.drstra.in/posts/a-misse… 👀👀👀
We built a vulnerability research pipeline, using an upcoming cyber model, to analyze the security of the Linux kernel. Besides finding and exploiting the found vulnerabilities, the agents discovered at least 10 new exploitation techniques that were new to us and some external kernel exploit experts we checked with.
More on the design and what we learned: openai.com/index/a-thousand-…
Sam Sanoop retweeted
my granny couldn't work out if she was affected by the eMudhra vulnerability, so I had the clanker build her a website
fixemudhra.com/
thought it might be useful for other people as well so sharing it here
Built on @Dennis__Jackson's work with just a tiny bit nicer UI
Sam Sanoop retweeted
With @hash_kitten, we've been looking into Cloudflare's /cdn-cgi/image endpoint and managed to get an XSS :D
To achieve this, we used what I believe to be a new CSP bypass involving the Cache-Control response header, combined with a sanitizer bypass!
I hope you'll enjoy it! 👇
Our security research team discovered a cross-site scripting vulnerability in Cloudflare's /cdn-cgi/image/ endpoint by chaining an SVG sanitizer bypass with a new Cache-Control header trick to bypass the CSP. The issue was reported to Cloudflare and has since been fixed.
You can read more here:
slcyber.io/research/cache-me…
Sam Sanoop retweeted
Brotli CVE-2026-111497 goes well beyond Node.js.
Quick search shows unpatched Brotli decoders in Java HTTP stacks, WOFF2 libs, CF workerd.
TLS certificate compression (RFC 8879) is another attack surface worth investigating.
Check statically linked Brotli copies.
Sam Sanoop retweeted
To teach a lesson,
After Wiz rushed to buy php2shell domain and use its marketing machine to steal the spotlight, I spotted "phpbleed" in a recent Calif tweet and bought phpbleed.com before wiz could pull the same stunt again.
A big budget can buy a domain. It shouldn't buy someone else's research credit.
If you have contacts at CISA or in the press, do the right thing: make sure the researchers who actually did the work get the recognition they deserve.
Hack the planet. Credit the researchers.
Sam Sanoop retweeted
The write-up from @moyix is finally out! It covers how we discovered three Chrome vulnerabilities: a V8 memory corruption bug and two sandbox escapes (one from V8 and another from the renderer), and chained them together into a full Chrome exploit that earned a $250K bounty!
xbow.com/labs/research/zero-…
Sam Sanoop retweeted
How Anthropic's new engineering post would read without the PR:
Seven engineers, assisted by Claude, built and migrated to a new source control system in five months, handling 30,000 merges a day and reducing infrastructure CPU and memory requirements by 200x.
The system builds on architectures pioneered by Google's Piper and Meta's Sapling/Mononoke, and uses Google Spanner for distributed metadata storage and cloud storage for file contents. So the team didn't have to build the distributed database, replication, consistency, or fault-tolerance infrastructure from scratch.
The implementation and migration are genuinely impressive. But much of the difficult underlying infrastructure already existed, and the architectural ideas have been used at scale for years.
There's also the question of what the numbers mean. Going from 2,500 to 30,000 merges per day measures how much code gets merged, not how much useful software gets produced.
So the valid claim is that Claude helped a small team rapidly implement and deploy a specialized source control system, using mature infrastructure and well-established architectural ideas.
Instead, we got this announcement: "At Anthropic, coding is no longer the bottleneck to building systems or doing research."
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
Series on Compiler and LLVM internals
P1: sh4dy.com/2024/06/29/learnin…
P2: sh4dy.com/2024/07/06/learnin…
P3: sh4dy.com/2024/11/24/learnin…
P4: sh4dy.com/2026/10/04/learnin…
#infosec





























