←
zhero;2,551 posts
zhero; avatar

zhero;

@zhero___

vulnerability researcher; seek the truth for a living

◷ Joined September 2019▧ 364 Photos and videos
zhero; avatar
zhero;@zhero___·Feb 5

My research, “Next.js, cache, and chains: the stale elixir” ranked 7th in the @PortSwigger top 10 web hacking techniques of 2025 I’m truly honored and grateful, this is one of the most meaningful recognitions for a researcher, thank you!

Post attachment
zhero; avatar
zhero;@zhero___·Nov 14

Swimming against the current is starting to get exhausting. ref: H1 signal: 6.74/7 (𝑝𝑙𝑒𝑎𝑠𝑒 𝑎𝑑𝑗𝑢𝑠𝑡 𝑡ℎ𝑒 ℎ𝑎𝑐𝑘𝑏𝑜𝑡, 𝑡ℎ𝑜𝑢𝑔ℎ) Intigriti: 100% valid

zhero; avatar
zhero;@zhero___·Nov 14

average experience on @Bugcrowd; > Analysts compulsively mark anything that exceeds their level of understanding as "Not applicable" > The platform is imposing limits based on its analysts' decisions > I can no longer work properly

Post attachment
Tom Stacey avatar
⟳ zhero; retweeted
Tom Stacey@t0xodile·Nov 10

How bad is header injection really? Watch @m4st3rspl1nt3r and I weaponize it to create Desync worms, capture credentials inside a CDN and inadvertently share our shopping cart with thousands of users. The recording for CRLF-Powered Desync Attacks is live! youtube.com/watch?v=PVOmWVF2…

James Kettle avatar
⟳ zhero; retweeted
James Kettle@albinowax·Nov 2

I've been nominated for the SANS Difference Makers Awards, in the Red Teamer category! I'd love your vote: feedback.sans.org/733559 If I win*, I'll share something that genuinely surprised me involving a website, a vulnerability, and GLM 5.3 #SANSDMA #DifferenceMakers *I'll also share it if I lose

zhero; avatar
zhero;@zhero___·Oct 30

I would add that you should make sure they actually pay what they promise in their own policy, and that their bounty table isn't just a marketing gimmick or some random() function.. Having worked with some of them, and ranked 4th all-time on one of the largest crypto exchanges, I can say that unfortunately, it hasn't been my best experience. The same goes for my peers.

Which crypto exchange is safe? Here’s a little “canary in the coal mine” signal for everyone outside security who’s asking me / DMing me. Search the exchange’s bug bounty. What’s the maximum reward? Minimum reward? Why does that matter? It’s a small representative window into how much they’re willing to invest in securing YOUR funds. It’s not perfect, but it’s a strong signal imo.

Post attachment
Gareth Heyes \u2028 avatar
⟳ zhero; retweeted
Gareth Heyes \u2028@garethheyes·Oct 27

XSS from a response header 🤯 Firefox will load an XSLT stylesheet from a data: URL in a Link header. Combined with a harmless XML body and you get JS running in the page origin. Plus Safari importing GIFs as SVG and more sanitizer bypasses

Post attachment
zhero; avatar
zhero;@zhero___·Oct 27

On a related note, the hackerone-agent has marked several of a colleague's cache-poisoning reports affecting page availability as N/A, immediately classifying them as DoS, even though some programs had accepted the same vulnerabilities shortly beforehand. At least 95% of programs accept these vulnerabilities, even when DoS is explicitly OOS. Such exclusions are partly intended to prevent disruption to production, which is not the case when a cache-buster is used to demonstrate cache poisoning without affecting other users. Making this distinction at the agent level, as has been done manually until now, would be greatly appreciated - @Hacker0x01

hackerone-agent just closed a report of mine as a dupe of another report - thats fine. I then suspected that there will be more endpoints with the same issue, fuzzed a lot and found an unrelated, reported... again dupe of the same one because a) same host b) same technique... thats strange... would love someone from @Hacker0x01 to look at that.

slonser avatar
⟳ zhero; retweeted
slonser@slonser_·Oct 27

We've been working with x402 for a while. Now that it’s taking off, we wrote down everything we’ve learned in an article Also, we've refreshed our website design. Check it out, along with our previous articles if you missed them 👇

We found multiple ways to bypass the 402 paywalls 💸 neplox.security/research/bre… :~$ "402 Payment Required" sat unused for 30-ish years - Now, the protocols reviving it let us skip the paying part; Here's how paywalls in TypeScript / Go / Java served paid content for free: [1] - x402 verify() checked the amount, the asset and the network; but not the recipient. What if we rewrite payTo in the console and payTo ourselves? 👀 [2] - MPP credential proved an invoice was paid, not what for. What if we pay 1 sat for /cheap, but spend it on the 100 sat /expensive? 👀 [3] - The middleware priced one path, the server served another; & here is just 1 example out of many: → GET neplox.security/premium HTTP/1.1 Host: app.example ← HTTP/1.1 200 OK { "served":"PREMIUM CONTENT" } <!-- READ MORE: "Breaking HTTP (pay)walls" --> 👉 neplox.security/research/bre…

SinSinology avatar
⟳ zhero; retweeted
SinSinology@SinSinology·Oct 21

To teach a lesson, After Wiz rushed to buy php2shell domain and use its marketing machine to steal the spotlight, I spotted "phpbleed" in a recent Calif tweet and bought phpbleed.com before wiz could pull the same stunt again. A big budget can buy a domain. It shouldn't buy someone else's research credit. If you have contacts at CISA or in the press, do the right thing: make sure the researchers who actually did the work get the recognition they deserve. Hack the planet. Credit the researchers.

zhero; avatar
zhero;@zhero___·Oct 9

Honored to have been invited by HackerOne to the Live Hacking Event H1-045 in Copenhagen, based on the Top Skillsets criteria. An event I unfortunately won't be able to attend due to personal reasons. A first for me, after all this time.

Post attachment
Kévin GERVOT (Mizu) avatar
⟳ zhero; retweeted
Kévin GERVOT (Mizu)@kevin_mizu·Oct 7

I'm happy that my first article as part of the @SLCyberSec research team is finally out! 😁 It covers an interesting ImageMagick race condition that I found back in June, which, combined with a polyglot payload, allowed me to achieve file read/RCE on Discourse. This should resonate with those who've seen the recent @HacktronAI research. I hope you'll enjoy it! 👇

Our research team discovered two vulnerabilities in Discourse: a pre-authentication cache poisoning to sitewide XSS (CVE-2026-55674), and an arbitrary file read (RCE) chaining a JPEG race condition with ImageMagick and Ghostscript (CVE-2026-55420). You can read more here:

Post attachment
zhero; avatar
zhero;@zhero___·Sep 30

I wrote a short, non-technical, relatively introspective draft about how I feel about the recent changes in independent vulnerability research. It won't resonate with everyone but feel free to give it a read: Draft of a grief: Research has changed, for better and for worse shortseason.substack.com/p/d…

Post attachment
zhero; avatar
zhero;@zhero___·Sep 22

average flow-state posture for high-impact research

Post attachment