Pinned Tweet
Guys & girls!
Exactly a year ago I promised over 15 bugs in win32k.
You're welcome to read and find out about my biggest research so far: #win32k #SmashTheRef bug class - github.com/gdabah/win32k-bug…
Check out the paper and the POCs, there are some crazy stuff going on. Promise!
True!
But the good thing is that in a few months once all the low hanging fruits vulns will be behind us, and it’s gonna hurt, it will be back to belong to the best researchers again.
I’ll be honest here.
I don’t feel the same excitement about iOS exploitation anymore like it was during the Lookout days in 2016 with the NSO exploit chains.
Today you can run commodity AI like DeepSeek, you run an AI swarm into a problem, it might cost you $3000 via API or nothing if you own some DGX, and you will find vulns. You will find the exact same vulns with $30,000 spent on openAI.
I think the only people left finding something are the ones building special fuzzing harnesses steered by an LLM to explore paths that weren’t explored before (there are already open source projects for this). And of course the upstream bugs that Apple keep introducing after each release.
Knowing that with an LLM you can reverse engineer anything end to end, plus you have access to better harness now and you can 1-shot your own:
Vulnerability research only constraints looks to be money (granted you have the skills already)
If you are rich you will find vulns.
If you are poor it means you missed all the previous cycles to make money on VR and you have a skill problem, or maybe you just started. If you just started it will be exponentially hard to find anything useful going forward the bar is extremely high and most importantly exponentially expensive.
Bad news for threat actors in cybercrime.
That leaves us with nation states or well funded firms / having resources to find new bugs.
If you are independent VR guy I wish you good luck.
Gil Dabah retweeted
Replying to @Tenzai_Labs
@Tenzai_Labs finished #1 on @Hacker0x01's VDP business leaderboard again this quarter.
Last Q we ran on US frontier models; this quarter we used GLM 5.2 & 5.3, open-weight models from z.ai.
We still came out on top, with just 3.5% false positives, and roughly 30% lower cost per report.
For us, it shows the harness matters more than the model underneath it - we built Tenzai to work with a choice of models.
The bigger point is the warning. Open weight models are freely available and highly capable to power offensive AI operations at scale. Attackers can and will build malicious agents with these models.
@nytimes covered it today: nytimes.com/2026/10/01/scien…
If you're defending applications, networks and infrastructure the window to test them continuously, before someone else does, is closing.
Full write-up on how we did it: tenzai.com/blog/an-open-weig…
Gil Dabah retweeted
Replying to @Charlesaf3 @pmarca
Yeah, really liked Emergence Capital. Gordon and Santi there are wonderful. But we could never get a deal with them because another partner was skeptical. Years later I ran into him and he said: “You know, I always thought you were completely full of shit, but you proved me wrong. My loss. Congratulations on all your success.” And I totally get it because early on we were full of shit but we figured it out, day after day.
Gil Dabah retweeted
Hackathons are a good excuse to build a slightly unreasonable version of the future.
So we built an entire computer inside the browser, designed for humans and agents to use together through WebMCP.
No access to your local machine. Just send an agent a URL and give it a fresh computer to work with.
Built by our awesome @ilay_alog 🦾🤖👑 !
We just submitted our project to the @OpenAIDevs WebMCP hackathon: The WebMCP Computer.
WebMCP Computer is an operating system that lives inside the browser, with WebMCP as its native control layer.
It is a computer that treats agents as first-class citizens, where files, processes, applications, windows, and the terminal are exposed directly through WebMCP.
You can send anyone one URL that becomes a disposable computer for any agent task.
We created a computer instance in ChatGPT Sites, open it with Codex’s in-app browser and try it here: computer.webmcp.com/
Some examples of what you can do with WebMCP Computer:
1/ Give a coding agent a fresh computer to clone a repository, edit code, run tests, and preview the result.
2/ Let an agent inspect logs, manage processes, change configurations, and repair a broken system.
3/ Give a research agent its own workspace to browse, download files, analyze data, and create a report.
4/ Create reproducible environments for evaluating and comparing different agents.
5/ Let humans and agents work together in the same environment, with the agent using WebMCP and the human using the GUI.
The list of applications is endless, with more examples in our GitHub. The project is fully open source under the MIT license.
github.com/nekuda-ai/webmcp-…
devpost.com/software/webmcp-…
Created by our awesome founding engineer @ilay_alog.
Gil Dabah retweeted
Big NEWS: Today we're launching Catch AI, an admin-assistant for busy executives.
We started Catch with a simple idea:
AI should actually do the administrative work executives hate doing themselves.
Not suggest. Not summarize. Do.
>>
Gil Dabah retweeted
Great time to share all the WebMCP tooling we’ve built lately:
1/ the first WebMCP directory
webmcp.com
2/ WebMCP extension for developers (batteries included)
chromewebstore.google.com/de…
3/ codex plugin to build WebMCP tools on your site
github.com/nekuda-ai/webmcp-…
The WebMCP Challenge is here.
We’ve teamed up with @ChromiumDev, @CloudflareDev, @ShopifyDevs, @vercel, @render, and @Netlify for a 10-day hackathon.
Up for grabs: $35,000 in cash prizes, Codex Micros, ChatGPT Pro subscriptions, and more prizes from our supporters.
Gil Dabah retweeted
Autonomous Security - EDT for AI Agents. Think CrowdStrike for Claude Code and Cursor.
a16y.ai
Gil Dabah retweeted
What a rotten deal we made with Iran. We get nothing (except laughter at our stupidity). They get everything, including delay and big cash!
Gil Dabah retweeted
FULL REMOTE CODE EXECUTION on default nginx 1.30.0 no config changes needed. 🫠
Verichains a deadly exploit chain combining Nginx-Rift (CVE-2026-42945) + Nginx-PoolSlip (CVE-2026-9256).
2-byte heap pointer overwrite & heap over-read then ASLR bypass to arbitrary command execution via system() on connection teardown.
Over the next few months, we'll be gradually publishing some of our internal security research.
Starting with a bug chain that turns Nginx-Rift + Nginx-PoolSlip into full RCE.
More to come.
#Nginx #1day #RCE
blog.verichains.io/p/two-byt…
Also worth to note that at my company we code review the results of AI generated code.
I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem.
As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)!
I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work.
It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results?
88ms => 1.5ms
150K allocs => ~500 allocs
Incredible right? Nope.
My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path.
This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput.
The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity.
Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.
We freeze versions and update a bit later. Unless it’s a critical security patch. Easier and safer.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
Why I am not surprised. Keep building like monkeys. It gets exposed with your cloud bills and now AI bills and next your security posture.
Cloudflare's security team spent the last few weeks testing Anthropic's Mythos against fifty of our own repositories. What we learned about offensive AI, why faster patching is the wrong reaction, and what the architecture around vulnerabilities has to look like next. cfl.re/49BRUqW
Real rock star!!
You have no experience.
You’ve never started a company.
You’ve never had a full time job.
Nike is going to kill you.
You’re a kid.
You don’t have technical skills.
You shouldn’t build hardware.
Apple is going to kill you.
You can’t build hardware.
You can’t measure heart rate non-invasively.
Athletes don’t care about recovery.
Under Armour is going to kill you.
It won’t be accurate.
You don’t listen.
You’re an ineffective leader.
You can’t recruit great talent.
You’re going to have to pay every athlete.
You can’t measure sleep non-invasively.
It’s too expensive to research.
Athletes are a small market.
The product costs too much to make.
The product costs too much to sell.
Your valuation is too high.
Consumers aren’t going to want it.
Hardware is too hard.
You should measure steps.
Fitbit is going to kill you.
You can’t build a marketing engine.
You can’t raise enough money.
You need a real CEO.
Google is going to kill you.
You can’t be a subscription.
You can’t build a brand.
You can’t do consumer in Boston.
Your valuation is too high.
You shouldn’t make accessories.
You shouldn’t make apparel.
Lululemon is going to kill you.
You can’t predict Covid.
Stay in your niche.
You are going to run out of money.
You can’t build a health platform.
Amazon is going to kill you.
You can’t measure blood pressure.
You can’t get medical approvals.
The market is too small.
You don’t understand AI.
The market is too competitive.
It won’t work internationally.
The supply chain is too complicated.
You can’t build an AI.
You can’t raise enough money.
It’s too competitive.
Healthcare isn’t going to want it.
…
Just keep going ✌️
One of the best hacking teams
I know. And this is only the beginning!
We evaluated @Tenzai_Labs AI hacker across six major CTF competitions designed for humans.
Result: Top 1% performance, outperforming 125,000+ human hackers across different domains - web hacking, ai hacking, low level system hacking.
We wanted to see what @Tenzai_Labs's hacking agent is really capable of in the most complicated and competitive environments, where to excel, one needs to solve increasingly difficult challenges.
The results we achieved surprised even me. This is incredible evidence of what AI agents with the right harness can do and I expect it to only get better from now.
blog.tenzai.com/tenzais-ai-h…




















