Calif retweeted
LLMs are great at finding bugs, but so are fuzzers. @5aelo compared the vulnerabilities found in V8 by BigSleep, an agentic system, with those found by the Fuzzilli fuzzer.
projectzero.google/2026/10/f…
Calif retweeted
Just dropped a new blog post! 🔥
blog.orange.tw/posts/2026-10…
Calif retweeted
Favorite part of talking with @lcfr_hax at @unpromptedconf is learning that he didn't do anything crazy with harnessing. He's just really fucking good at hacking PHP and also happens to have Codex. Such a friendly and humble dude.
Don't just "use AI". Keep learning.
Calif retweeted
You definitely don’t want to miss @calif_io Quang “the prodigy” L’s talk at @offensive_con JP 😎
Calif researchers are at Unprompted, presenting zero-click attacks and php2shell. You don't want to miss this!
Tue Oct 27, Stage 1, 16:45, "0-Click Remote Exploits in an AI World" with @pwnlambda and @brucedang
Wed Oct 28, Stage 1, 14:45, "PHPocalypse: Finding, Exploiting, and Disclosing php2shell" with @lcfr_hax and @XorNinja
Calif retweeted
Automating Myself Out of a Job, Badly: Guest to Host on Apple Virtualization by @blacktop__
Calif retweeted
This weekend I had Codex rewrite the iOS Gravity tweak to work with the code execution primitive of my chain so I could have a fun demo like @calif_io
Luckily it survived the 27.2 update. No this isn't a full jailbreak, just a powerful sandbox escape.
I just remembered why Brotli looked vaguely familiar: I worked on it at Google. I even co-authored an RFC [1]. Hopefully they haven't found my bugdoor 😅
Joking aside, CRIME [2] led me to work on things like Brotli and HPACK, the header compression scheme used in HTTP/2.
That was the magic of working at Google. They operated at such a huge scale that a few weeks of your work could become part of a widely used Internet standard. One of my fondest memories is helping audit QUIC and writing little bits of crypto code for it.
Before I left Google, a teammate on the Tink [3] team told me he believed Tink would last 50 years, outliving everyone on the team. Tink is now in its 10th year. 40 more to go!
I also learned that breaking things is fun, but lasting contribution often comes from building things that make the Internet faster and safer.
That same belief shapes much of our work at Calif. People know us for our offensive security research, but we've also done a lot of security engineering to harden systems and mitigate attacks, from large-scale Rust migrations to fast sandboxing or reducing zero-click attack surface in mobile apps.
We'll be sharing some of that work soon. Stay tuned!
[1] rfc-editor.org/rfc/rfc9841.t…
[2] en.wikipedia.org/wiki/CRIME
[3] github.com/tink-crypto
Calif retweeted
Sorry folks, we have a confirmed PHP compromise with post-exploit activity. Still not the widespread outbreak we all braced for, but it’s actively exploited in the wild. Updated threat brief:
unit42.paloaltonetworks.com/…
This is too far.
First our fav restaurants shutdown their booking websites because the NSA told them so, now they refuse to serve broccoli.
Calif retweeted
A brief update on the critical vulnerabilities in PHP:
We have not yet validated exploitation in the wild and we have no evidence of successful wide scale exploitation. There are currently several exploit PoCs publicly circulating, many of which appear to be "vibe-coded" and are incapable of remote code execution. We have validated some PoCs, however, that are capable of RCE against default deployments of mod_php but not PHP-FPM.
Nonetheless, exploitation may have already begun in a limited fashion and the threat is viable and very serious. Defenders should:
1) Patch & Restart by upgrading to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35 and restarting web services
2) Layer Temporary Safeguards at the network edge (WAF/proxy rules) and server configuration level if immediate patching requires a maintenance window
3) Protect Credentials by monitoring for abnormal session traffic and rotating keys and passwords on compromised internet-facing PHP systems exposed prior to patching
🔗 We are continually updating our Cloud Security blog post on this topic with real-world guidance and actionable defense strategies as we learn more. Please keep monitoring these posts for updates as you prioritize your patching efforts: cloud.google.com/blog/produc…
🔗 Technical details from Wiz: wiz.io/blog/php2shell-php-rc…
🔗 Details of the exposure from VirusTotal: blog.virustotal.com/2026/10/…
Calif retweeted
Replying to @deedydas @abliteration_ai
Which vulnerabilities? Because the PHP one was found with Sol. Which has safeguards.
Although I realise that doesn’t fit your narrative and is of course therefore ignored =)
Calif retweeted
A liability with a timer on it:
tolmo.com/blog/faster-than-a…
Calif retweeted
The @UnpromptedAU videos came out recently. Check out my ramble about AI assisted exploit development unprompted.au/videos/ai-assi…
Calif retweeted
Reproduced the Brotli memory corruption bug (CVE-2026-111497) using a simple Node.js + Express app.
Patched and unpatched versions produce different decompressed output, making it possible to remotely identify vulnerable servers.



















