
26 | Bug Bounty Hunter @bugcrowd & Pentester at @inspectiv
Joined March 2021
- Tweets9.1K
- Following419
- Followers20K
- Likes8.4K
Pinned Tweet
Thank you @Bugcrowd @inspectiv @Hacker0x01 ❤️🔥
This video is for those who think their life can’t change from where they are.
Mohsin Khan retweeted
All credits to pro @tabaahi_ tips only.
Follow me for such tip 😄 😜😅😂
Here it is, just from 2 platforms, external bounties and other platforms are additional. All from deepseek 4.1 Flash.
Monthly billing around $3000 for Deepseek API
BTW thanks to @Bugcrowd & @Hacker0x01
And Special thanks to @ThisIsDK999
Need suggestions for buying another MacBook. 👀
Currently using a MacBook Pro M4 with 24GB RAM. What would you recommend as my next upgrade, To run my hackbot!
I've been working with this customer for more than a month, and everyone on the team has been amazing. I'm excited about the findings from these submissions and look forward to more great results together!
They triage in 24 hours btw.
Mohsin Khan retweeted
For the second time in Google Chrome’s history, Google awarded a $250,000 bounty for a full-chain exploit… to @XBOW. Here’s the full story:
At an all-hands at the start of 2026 in Malta, I set the team a crazy challenge. A full-chain exploit of Chrome by the annual Black Hat cybersecurity conference in August.
I believed there were few better tests of whether @XBOW could move beyond web applications to desktop software, servers and devices.
Chrome is one of the most hardened pieces of software on the planet, used by more than half the world’s population.
A full-chain exploit lets an attacker take total control of a machine, where they can read every email, password and bank login the user types. You don’t need to download anything or click a phishing link. Visiting the wrong site is enough.
So @moyix, Andres Luksenberg, Baul Lee, and Willem Pinckaers took on the challenge along with a fifth teammate: OpenAI's GPT-5.6 Sol.
They built a chain they thought would win, but Google told us they already knew one of the bugs.
We were already in Las Vegas for Black Hat and DEF CON, and the team didn’t want to go home without the win.
So Brendan and the agents built a new exploit in just 6 days.
We submitted it to Google and waited.
The news came through that we'd done what should’ve been impossible. A full-chain bounty of $250,000, the first awarded under Google’s 2026 rules.
It took just 6 days and $40,000 of compute to construct an exploit that affects a billion users of Chrome on Windows. An intelligence-agency veteran told me his team used to spend 6 months on this kind of vulnerability.
My takeaway: the cost of finding truly critical vulnerabilities is collapsing, for attackers and defenders alike. Restricting powerful models is not the answer; GPT-5.6 Sol is already public.
But defenders have one advantage attackers never will: they can test their own code first.
Assume your software is exploitable. Whoever is hunting your bugs has the same building blocks we did.
This is cause for urgency but not panic.
XBOW is now developing an autonomous product for testing compiled software (desktop applications, servers, embedded devices), and partnering with the world’s top organizations to design that product.
If you’d like to be one of them, get in touch.
P.S. Restart Chrome whenever the Update button appears!















