Abhishek (@aacle_) header
Abhishek (@aacle_) profile picture

Building @Vulncure ⚡ Better SaaS security shouldn't cost a fortune. AI-powered vulnerability finding & code fixes from $49/mo ↓ waitlist open → https://nitter.gq/t.co/XkcGeBREXr

Joined June 2017
Good findings 🙌
first five digit payout
10
546
A Claude Code hackbot started with ~80% false positives. its creator built a second bot to prove the first one wrong. 126 bugs submitted. 112 confirmed as real or duplicates. I Studied 10 AI bug-hunting cases. Here's what worked 👇 medium.com/@Aacle/i-study-10…
5
5
32
2,275
Google paid $90,000 for an RCE that started with a Flask session cookie. The cookie leaked its own signing secret. 💀 Forge the cookie → 𝚙𝚒𝚌𝚔𝚕𝚎.𝚕𝚘𝚊𝚍𝚜() → unauthenticated RCE Insane find by Simon keock. simonkoeck.com/writeups/goog…
1
1
22
1,105
why is everyone suddenly focused on building better harnesses rather than just relying on better models?
6
1,063
imagine getting RCE just by making someone open an email. 💀 that's what researchers demonstrated with Upload2Shell. a disguised attachment → thumbnail generation → Ghostscript → RCE. no attachment click needed in the tested Roundcube setup. pwn.ai/upload2shell
Good morning, we are releasing Upload2Shell - where you upload a file and get a shell. We wrote about a single vulnerability that turned file uploads, email attachments, & even print jobs into remote code execution paths across Debian 13, Google, WordPress, Roundcube, etc...
1
7
963
Funny how things change. A few years ago, people who used AI to find vulnerabilities were criticized by those who believed in manual hunting. Even using AI to help write vulnerability reports was looked down upon. Now, many of those same people are using AI in their own workflows. The lesson? Don't criticize a tool just because you haven't figured out how to use it yet.
731
Everything is changing fast.⚡️ hackerone's 2026 report is wild. - $89M paid out in a year. - 85% of researchers upskilling in AI. - 68% shifting toward more complex, higher-paying bugs. low hanging fruit is crowded. chains are what's left. the real edge now? logic flaws, creativity, and chaining bugs.
2
1
44
1,749
finally got our scanner to a point where it feels… real. 👀 one scan. here's what happened: → 51 specialized scanner units → working together in parallel → 24 findings → 6 critical → 2 high → 15 medium and here's the interesting part: it's not just one AI agent running a bunch of checks. it assembles an entire team of specialized agents, lets them collaborate, validate findings, and put together the final report. watching this actually work is something else. 🧪
4
5
1
48
4,650
Java rejected the malicious Base64 input. But only AFTER writing 62 bytes past the buffer. That’s Java4Shell (CVE-2026-114938): a 9.2-rated OpenJDK flaw that Calif turned into pre-auth RCE. A memory-safe language. An unsafe optimization. A critical bug. calif Walkthrough 👇
2
5
52
3,887
I haven't shared much about what we've been building behind the scenes. But today, I want to share something I'm genuinely excited about. For months, we've been working on a security scanner with one goal: Make powerful security testing accessible to everyone. Not just big companies with big budgets. And honestly, the results have exceeded our expectations. We're seeing some areas where our scanner performs better than tools widely used by enterprises. As someone who's spent years finding vulnerabilities, seeing this come together feels incredible. We're getting closer to launch. And I can't wait for you all to try it. ❤️
3
1
6
944
Bug bounty hunters on a $0 budget, this one's for you. 🐛 DeepSeek V4.1 Flash is available for FREE on OpenCode. And OpenCode actually gives you pretty generous usage limits. But what if you hit those limits? 👀 Here's a little trick: You can chain multiple WSL distros and keep using it, almost like unlimited usage. Go hunting. Good luck! 🚀
15
43
398
25,096
correction (wrong image was uploaded with wrong model)
8
2,823
🚨BB Tip : WAF evasion with weird chars Here’s the thing: attackers hide simple payloads (eg. 𝗰𝗮𝘁 /𝗲𝘁𝗰/𝗽𝗮𝘀𝘀𝘄𝗱) by stuffing params with backslashes, \x.. hex, IFS, and odd punctuation (|/???/\b**\h). Don’t match raw strings — normalize first, then detect. 👉Quick checks: Decode repeatedly until stable, then run signatures. Flag mixed-encoding or repeated escape sequences. Use allowlists for expected param formats.
37
1
298
9,311
Five critical NGINX remote code execution vulnerabilities Takeaways I even don't know how many sites are actually effected with the NGINX2Root Vulnerabilities that still didn't patched effectively
1
2
1,015
saw this on r/claudecode and it's getting reposted everywhere. a dev had claude code working on his codebase for weeks. then he asked it to stop coding and use the product like a buyer. click through the app, try to buy the thing, act like a customer. it found bugs it had never noticed in all those weeks of working on the same code. same agent. same repo. different role, different bugs. coder moder reads files looking for whats's wrong with the implementation. buyer mode walk the flows a real user walks, and those are the flows nobody scripted the edge cases for. hunters already know this. you always find someone else's target what its author walked past for years. agents inherit the builder's blind spots, and switching roles is how you borrow a fresh pair of eyes.
4
1
9
1,700