Colby retweeted
Happy election day!
After voting, enjoy this blog post about why we still use paper ballots.
If you aren't voting today, you are not allowed to read the post. It's the rules.
A cryptographically verified tally doesn't mean every vote is legitimate. Paper ballots still matter: they provide an audit record independent of software. We explain how electronic voting works, and how cryptography can make paper-based elections more trustworthy. blog.trailofbits.com/2026/11…
Special election day blog by the @trailofbits crypto team. Learn how electronic voting works:
nitter.gq/TheMijCipher/status/21…
We're using our work on Patch the Planet as a "school for agents" -- we discover methods to solve the toughest problems, then deploy the solutions at scale with agents.
Stable software often ships with known bugs because the fixes are never backported. That backlog is now an easy target for cyber-capable agents.
We used Codex to cut time per backport from days to ~30 min, with 149 Linux kernel CVE fixes applied so far.
blog.trailofbits.com/2026/11…
Colby retweeted
Btw we released Pwndbg 2026.10.28 - github.com/pwndbg/pwndbg/rel… - mainly with a few fixes, the most important one is the LLDB portable build that crashed in previous release
Colby retweeted
Crypto hacks in 2026 are already 71% above the 2022–25 annual average, per DefiLlama.
AI helps attackers find bugs faster, and defenders need the same edge to fix them. At @summit_defi in Mumbai, @nisedo is sharing lessons from our AI auditing work, including Patch the Planet.
Colby retweeted
We achieved RCE via Brotli in Linux labs:
• Node.js 24.22.0 + Express 5.3.0 (x86-64/ARM64) through its standard JSON parser
• Electron 41.10.7 (x86-64) using a custom-built decoding service
Getting it to work requires a carefully matched setup and can take repeated attempts.
We’re still testing how exploitable the Node.js/Brotli bug is, but we’ve found that it’s surprisingly hard to tell whether you’re even affected.
So @ToBScottA built a scanner that finds hidden copies of the decoder, even in stripped binaries.
github.com/trailofbits/brotl…
You’ve prompted your agent “find bugs, make no mistakes” five times already. Now what?
At @summit_defi I’ll share five practical techniques to find real bugs, push their impact further, and check what your agents actually reviewed.
All in five minutes.
Replying to @nisedo
@nisedo · DSS 2026
“AI-Native Auditing in Five Minutes: Questions, Evidence, Coverage”
Which talks are on your shortlist? Share yours:
defisecuritysummit.org/2026/…
Tickets: luma.com/9qtxqqxx
Colby retweeted
Our demo shows PHP2Shell giving a shell on MediaWiki, Symfony, Laravel, and phpBB.
We’ve confirmed exploits work on pre-patch releases of PHP 8.2–8.5. If you haven’t updated, assume attackers can compromise your server, and that exploitation will only get easier.
Update: Our PHP exploit is now production-grade.
* stock php.ini-production, display_errors=off, normal memory_limit, multi-worker, ASLR, under load
* ARM64 + x86-64 targets
* MediaWiki, WordPress, phpBB, Laravel
* Apache/mod_php and nginx/php-fpm -> root
nitter.gq/dguido/status/21131291…
Happy to have helped LiteLLM recover from this incident behind the scenes
We have completed our investigation into the attack chain behind the v1.107.0 release. Read it here: docs.litellm.ai/blog/securit…
Update: Our PHP exploit is now production-grade.
* stock php.ini-production, display_errors=off, normal memory_limit, multi-worker, ASLR, under load
* ARM64 + x86-64 targets
* MediaWiki, WordPress, phpBB, Laravel
* Apache/mod_php and nginx/php-fpm -> root
nitter.gq/dguido/status/21131291…
Re: the widely circulated blog claiming the PHP bugs aren't easily exploitable: @trailofbits has a working exploit that gets a shell on an unmodified MediaWiki installation.
eliastaylor.com/noexploit/
Replying to @jonoberheide @matthew_d_green @waral555 @OpenAI @AnthropicAI @daveaitel @halvarflake @benhawkes @chrisrohlf @trailofbits
That's precisely where Patch the Planet came from. I wrote up the origins here:
illusivedan.com/writing/patc…
Colby retweeted
We’re still testing how exploitable the Node.js/Brotli bug is, but we’ve found that it’s surprisingly hard to tell whether you’re even affected.
So @ToBScottA built a scanner that finds hidden copies of the decoder, even in stripped binaries.
github.com/trailofbits/brotl…
As part of Patch the Planet (openai.com/index/patch-the-p…), we found hundreds of bugs across 70+ open-source projects using advanced AI, including in some of the world’s most reviewed code.
We learned a ton along the way and at @summit_defi I’ll share some of those lessons and how they can be applied to DeFi.
Replying to @nisedo
@nisedo · DSS 2026
“Patch the Planet: Three Lessons for DeFi from AI Bug Hunting”
Explore the talk and add it to your agenda:
defisecuritysummit.org/2026/…
Tickets: luma.com/9qtxqqxx
Attackers have agents hunting for bugs. We need agents writing patches just as fast. @trailofbits is doing the work to make this happen reliably:
nitter.gq/trailofbits/status/211…
Finding bugs is the easy part. Shipping fixes that hold up is harder.
We analyzed thousands of Codex sessions from our work on Patch the Planet with @OpenAI and built patching-bugs, a plugin that writes a fix, proves it, and checks it for regressions.
To prove a fix, the plugin checks that the original code fails, the patch passes, and reverting the patch brings the bug back.
patching-bugs hands each fix to regression-hunt, our second new plugin. We ran it on the patches behind 21 known regressions, and it reported 25% fewer false positives than a baseline Codex agent.
Both plugins work best when your repo has a THREAT_MODEL.md and a PATCHING_GUIDELINES.md. blog.trailofbits.com/2026/10…
Colby retweeted
“You want to find the bugs, but it’s only good if you can also fix them.”—@anishrnaik on Risky Biz.
Many open-source projects have only a handful of maintainers, and fixes are falling behind. We’re building a reusable toolkit to help.
Full pod: youtube.com/watch?v=6SIgPjQ9…
Re: the widely circulated blog claiming the PHP bugs aren't easily exploitable: @trailofbits has a working exploit that gets a shell on an unmodified MediaWiki installation.
eliastaylor.com/noexploit/
Colby retweeted
Yesterday, rumors started circulating about two unpatched critical-severity bugs in PHP.
Within 17 hours, Cloudflare was blocking attacks and Patchstack reported active exploitation.
When AI can develop a working exploit in hours, bugs need to be patched just as fast.
Each day without a fix carries the risk that an attacker will find and exploit the bug. But it takes time to create a working patch, and PHP's patch was more complex than most.
The patch changed 402 files and added more than 11,000 lines, reworking core engine behavior that dozens of extensions depended on. The bug was reported on Aug 11, and fixes were shipped 71 days later. But less than a day after details leaked, systems running PHP were already under attack.
Patching needs to keep up with the pace of bug discovery. For the past four months, we’ve worked directly with open-source projects as part of Patch the Planet to understand how AI can expedite patching. Our ongoing research and work show that project-specific documentation, skills, and plugins can be embedded at the repo level to give agents and contributors access to the context maintainers carry in their heads: what counts as a bug, how a fix should look, and what can't break.
Our two new open-source plugins, patching-bugs and regression-hunt, are a first step toward a generalized set of tools and guidance for getting a working patch out faster: blog.trailofbits.com/2026/10…
PHP’s account of the incident: thephp.foundation/blog/2026/…
Colby retweeted
Security engineers should take note, because this is going to impact them very soon if it hasn't already.
Finding good bugs used to be a bottleneck, but frontier LLMs are shifting that bottleneck to patching. It's critical we keep up with the rate of bug discovery.
Finding bugs is the easy part. Shipping fixes that hold up is harder.
We analyzed thousands of Codex sessions from our work on Patch the Planet with @OpenAI and built patching-bugs, a plugin that writes a fix, proves it, and checks it for regressions.
To prove a fix, the plugin checks that the original code fails, the patch passes, and reverting the patch brings the bug back.
patching-bugs hands each fix to regression-hunt, our second new plugin. We ran it on the patches behind 21 known regressions, and it reported 25% fewer false positives than a baseline Codex agent.
Both plugins work best when your repo has a THREAT_MODEL.md and a PATCHING_GUIDELINES.md. blog.trailofbits.com/2026/10…
















