Prev founded Percy, Respondly, & Favstar. Family guy who enjoys 🍦⛷ Ξ. Bug hunting for fun and profit. 👨🏼‍🍳

Wanaka, New Zealand
Joined April 2008
Becoming adept at using a weeks worth of tokens in a day. Thanks @thsottiaux.
Day 18/ Decisions API is GA, OpenResponses joined the Linux Foundation, we shipped some performance improvements and Uber is going all-in on codex & work. But yes… that’s a reset!
23
Tim Haines 🇺🇦 retweeted
Thanks a lot to @TimHaines for performing a security audit of Rack Gateway: github.com/DocSpring/rack-ga… I've been working hard on this project and I've been trying to make it as secure as possible, but Tim was able to find a huge number of things that I had missed.
2
1
113
Interesting facets coming out of the PHP foundation's reports about Mythos and Daybreak Red not finding the bugs disclosed this week.
wait, PHP was actually scanned by Anthropic’s Claude Mythos earlier this year. they also had access to OpenAI’s Daybreak Red for validating exploits. the PHP Foundation revealed this JUST yesterday. keeping frontier cyber models in the hands of a selected few doesn’t seem to be working well for the internet. thephp.foundation/blog/2026/…
91
.@kong has also just bumped it's @Hacker0x01 signal requirement from 1 to 3. Hope this helps reduce the noise @sonicaghi. Would be interested to hear your teams experience with it over the coming month.
Interesting. @brave was paused for new report submissions on @Hacker0x01. They've unpaused, but have set a signal requirement of 7.0 (max value on H1) in order to submit. Seems like a much better way to manage volume. Your doing @bcrypt? Other programs with custom signal levels:
1
201
TIL github has a revoke token API. I know because Sol just used it to revoke 2 of my tokens. 😤
1
173
Tim Haines 🇺🇦 retweeted
-----BEGIN RSA PRIVATE KEY----- 4 -----END RSA PRIVATE KEY-----
247
3,939
325
41,660
1,055,749
Interesting. @brave was paused for new report submissions on @Hacker0x01. They've unpaused, but have set a signal requirement of 7.0 (max value on H1) in order to submit. Seems like a much better way to manage volume. Your doing @bcrypt? Other programs with custom signal levels:
4
1
2
861
If you're below the 7.0 signal required for Brave, you can submit using the trial report system. If your reports are triaged/resolved, you can keep submitting, even when not meeting the signal.
76
Back to burn mode.
Day 17/ Bet you thought we forgot, but no, it’s reset day today. Also good time to remind you to get Daybreak Blue access, it only takes 15 mins and you don’t want to have to do it in the middle of an incident.
104
My wife’s pharmacy has taken their php app offline, so she can’t pre-order her medication. (Need to submit a photo of the script)
1
225
Time for @chainguard_dev to remove 'trusted' from their bio.
Replying to @chainguard_dev
"On October 21st at 07:41 UTC, more than six hours before the coordinated release, Chainguard unilaterally broke the embargo and published built images containing the fix. Like other distributors, Chainguard had received the patch in advance so its users could update the moment the vulnerabilities were disclosed. Any attacker could now study the fix in binary form while every other PHP user was still waiting for the release. This disregarded weeks of work by many parties toward a coordinated disclosure." thephp.foundation/blog/2026/…
2
288
Hope your vendors patched. 🔥
Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
208
Exciting week for cybersecurity. 🔥🔥🔥
1
163
The “Leak and disrupted disclosure” section of this report is fascinating. Does Chainguard get excluded from future co-ordinated disclosures as a result?
231
Imagine sending a report in to a bug bounty program, and getting a dupe because OpenAI was monitoring your work and filed it a minute before you.
Replying to @maxious
Very strange how this keeps on happening
1
2
24
867
Tim Haines 🇺🇦 retweeted
OK so today we had - PHP2Shell - LiteLLM supply chain attack - Node2Shell - Gitlab CVSS 10.0 what next? 🫠
Another one 🚨 Gitlab is vulnerable to remote code execution. 1. Firewall your Gitlab server 2. Patch. CVE-2026-110264 is a CVSS 10.0 unauthenticated RCE in GitLab’s regex compiler. It reaches self-managed CE/EE instances back to version 7.0, while @gitlab.com is already patched. If you self-host GitLab, upgrade ASAP.
8
8
52
7,265
Tim Haines 🇺🇦 retweeted
I am here once again to say “put up or shut up” One million to open source this year, as we continue to give back to the ecosystem via the pledge. More than half has gone directly to your favorite open source developers. blog.sentry.io/another-year-…
34
45
12
408
33,703
Published: RubyGems[.]org hid 27 privileged admin actions from org members without admin access. 🙈 Hidden button ≠ authorization. Direct POSTs to Add Owner, Reset 2FA and Change Email still worked. Gem and account takeover despite TOTP + WebAuthn. github.com/rubygems/rubygems…
1
4
890
Is LiteLLM really worth using?
LiteLLM was compromised (Again). The latest version 1.107.0 contains an infostealer and RAT Will post more info as it comes in as a thread
1
4
1,270
This PHP bug is going to drop 11pm Tokyo time. Worth staying up for or no?
2
564