SOTA models + sota talent & experience + AI mindset = exponential productivity gains, while exponentially magnifying our mediocrity
Vinh Nguyen, a former chief data scientist at the NSA, said the WeChat worm was one of the most troubling and potentially severe cyberattacks he had ever seen, capable of reaching hundreds of millions of devices within hours. nytimes.com/2026/09/08/us/po…
Still the best of the best, completely different from all those "LLM-in, LLM-out" write-ups, and I always come away from it with something new to think about.
During my time at @QED_Audit I circled back and took another quick look at browser/JSE vulnerability research. AI agents flying high, seemingly finding & exploiting bugs everywhere, and there's this: a **constant integer overflow** in V8, alive for over 3.5 years. (1/5)
The world has become completely unfamiliar.
chromium-review.googlesource…
Please, have some empathy...
docs.google.com/spreadsheets…
This is spaghetti as hell😅
Root cause of Google Chrome V8 ITW (CVE-2026-11645)[506689381]:
TryFastAddDataProperty[1] needs a fast MAP[5]. But "after" checking[2], Map::PrepareForDataProperty[3] manages to normalize the map. The patch[4] rechecks for slow dictionary MAP afterwards.
chromium-review.googlesource…
Welcome to the $500 era!
[$500][508811474] High CVE-2026-9896: Out of bounds write in V8. Reported by 303f06e3 on 2026-05-02
chromereleases.googleblog.co…
I skimmed through the paper and source, still confusing about why do we need the model to reach arw/arce for evaluating the capability to exploit a v8 rce bug, any ideas?
I will never understand the urge to compare LLMs to fuzzers, and the narratives of LLMs are "just" pattern match😅, we still need humans for complicated and organic bugs!
[0/1]
Replying to @Void_Sec
Bug count != exploitable bug. Finding != chaining.
LLMs are exceptional at pattern recognition on known bug classes. They are not reasoning about novel failure modes in complex multi-component systems.
The hard bugs still require humans. voidsec.com/ai-vulnerability…
1377 High-yield Nukes retweeted
The Supply Chain - A New Hope: The Era of AI and its impact
A new article is out!
medium.com/@maor_s/the-suppl…
A v8 dcheck == $500, I would start searching for how to find XSS & CSRF bugs right now.
📣📢 Calling all Android and Chrome bug hunters 🧑💻🔎!
We're updating our Android & Chrome VRP programs to ensure we can continue to reward the most challenging and impactful vulnerabilities researchers find in our products. For details, 👇
bughunters.google.com/blog/e…
1377 High-yield Nukes retweeted
AI is changing the market value of bug bounty (increasing density of researchers, discoveries necessitates a change in incentive structure).
Interested to see what this does to OSS security
⚠️ Update: The Node.js project's security bug bounty program is being paused.
Reporting remains unchanged, and so does our commitment to security.
More details here: nodejs.org/en/blog/announcem…
composer 2 is kimi k2.5 with RL. the IDE is vscode. authorized or not, the entire $50B product is built on open source foundations other people created.
nothing wrong with building on open source. that's what it's for. but the people training these models should be getting more credit and more money than a wrapper company that evaluated base models and picked the best one.
Traditional fuzzers generate/mutate samples, what if we have meta-auto-fuzzers which could generate fuzzers?🤔
I packaged up the "autoresearch" project into a new self-contained minimal repo if people would like to play over the weekend. It's basically nanochat LLM training core stripped down to a single-GPU, one file version of ~630 lines of code, then:
- the human iterates on the prompt (.md)
- the AI agent iterates on the training code (.py)
The goal is to engineer your agents to make the fastest research progress indefinitely and without any of your own involvement. In the image, every dot is a complete LLM training run that lasts exactly 5 minutes. The agent works in an autonomous loop on a git feature branch and accumulates git commits to the training script as it finds better settings (of lower validation loss by the end) of the neural network architecture, the optimizer, all the hyperparameters, etc. You can imagine comparing the research progress of different prompts, different agents, etc.
github.com/karpathy/autorese…
Part code, part sci-fi, and a pinch of psychosis :)
1377 High-yield Nukes retweeted
Great article. Two questions after reading:
- There are certain skills needed for a researcher to succeed at low (vs. high) points in the abstraction stack. How much do they overlap?
- How do we reason about the economics of VR if we don't feel the true unsubsidized cost of AI?
Shrinking Margins: Frontier models don't perform vulnerability discovery the way traditional tools do, they reason through code the way humans do, and the margin left for human researchers is rapidly shrinking.
secure.dev/shrinking_margins…
👍🏻
My experience on how to play with openclaw
Managing AI agents is a management problem, not a prompt engineering problem.
atum.li/en/blog/openclaw_pri…
I decided to try out agentic coding/reversing, so I’m releasing a project that assists with reverse engineering in both Binja and IDA Pro. It’s an agent, not an MCP, that support multiple providers, it has some interesting features such as code exploration
github.com/buzzer-re/Rikugan




























