DestroyerX (@ide9x) header
DestroyerX (@ide9x) profile picture

I'm Ahmed, also Known As DestroyerX | wannabe Security researcher | الْحَمْدُ لِلَّهِ

./ MA
Joined July 2024
Photo by DestroyerX (@ide9x)Photo by DestroyerX (@ide9x)Photo by DestroyerX (@ide9x)Photo by DestroyerX (@ide9x)Photo by DestroyerX (@ide9x)Photo by DestroyerX (@ide9x)Photo by DestroyerX (@ide9x)Photo by DestroyerX (@ide9x)Photo by DestroyerX (@ide9x)Photo by DestroyerX (@ide9x)
الحمدلله و الشكر لله وحده Yay, I was awarded a $,000 bounty on @Hacker0x01! hackerone.com/iide9x #TogetherWeHitHarder my first 4-digit bounty ever. been waiting for this for months. #BugBounty #Hacking #Cybersec
28
4
218
8,640
DestroyerX retweeted
I'm so tired of reporting bugs and waiting days, weeks, or even months for them to be triaged, only to wait several more weeks for the client to respond.
11
1
96
3,436
DestroyerX retweeted
now its right
only looking for 10.0s today!! 😤 🤑
3
5
49
1,328
الحمد لله Happy to share that i’ve crossed +1k Reputation on @Hacker0x01 ! #HackerOne #BugBounty #hacking
7
102
2,064
I highly recommend this for Bug Bounty.
MiniMax M3.1 Flash is now free in OpenCode
24
72
4
2,037
83,439
DestroyerX retweeted
HackerOne really seems to have the fastest triage now. They have stepped their game up.
12
1
169
8,134
DestroyerX retweeted
Replying to @0xConda
Now we just need programs to start paying quick again and we’re back baby! One of my fav programs went from 2-3 weeks to 6-8weeks. Kills motivation big time
2
1
51
2,463
DestroyerX retweeted
can triagers wake up and triage my bugs so i can sleep in peace
14
6
1
132
10,884
Back before AI, hacking was actually fun. Leaked creds, vulnerable WP plugins, cPanel, mass exploiting new CVEs with scripts that takes you ages to write, defacing with really bad HTML that u stole from an other hacker. Now nothing’s fun anymore, even hacking NAZA is boring now.
21
19
2
352
15,507
that was a crazy find by deepseek flash sadly i'm late for Only 1 Week 😔 #BugBounty #Hacking #Hunting #hackerone
11
196
14,688
DestroyerX retweeted
In this article, I break down how I built OSA, the architecture behind it, the tools I use, and the lessons I’ve learned along the way.
14
72
1
446
17,811
DestroyerX retweeted
I built a vulnerability scanner extension for Burp Suite by @PortSwigger . It scans all http traffic history for : XSS, IDOR, SQLi & more... using custom skills, generated PoCs and a findings dashboard. Watch the demo and give it a try 👇 github.com/zack0x01/burp-sec…
24
109
5
707
34,297
DestroyerX retweeted
this bug report has seen 5 iphone launches and zero updates
24
18
1
382
17,991
DestroyerX retweeted
We hacked ChatGPT (using ChatGPT). We demonstrated that a single shared link could take over the account of anyone who opened it: private chats, files, settings, all of it. OpenAI rated it P1 and fixed it Oct 26.
23
40
14
341
42,597
DestroyerX retweeted
Everyday is Zeroday
BREAKING: Binance has been hacked with wallets across the Ethereum, Bitcoin, and TRON networks seeing outflows of -$5.7 billion. The hack includes $1.45 billion worth of Bitcoin and $875 million worth of ETH. If confirmed, this would mark the biggest hack in crypto history. We expect more information shortly.
3,691
5,911
1,293
60,860
7,717,852
DestroyerX retweeted
Start hunting
19
35
4
304
8,530
I started reverse engineering the patch for the critical PHP CVEs live on the @ctbbpodcast Discord, with the goal of building a PoC. The catch is that I can't use AI for anything beyond basic code exploration (basically, a glorified CTRL+F). The amount I've learned about PHP and memory exploitation is INSANE. I'm not saying I wouldn't have learned just as much with AI, but it wouldn't have been nearly as fun. At the end of the day, I tried asking AI some basic questions about the CVE and realized just how much it overcomplicated things. How bad it is at explaining things simply. If I'd started by relying on AI to understand the vulnerability, I might've actually taken longer to get anywhere close to the level of understanding I have now.
2
4
125
5,604
DestroyerX retweeted
gotta give it to @OpenAI and their sane daybreak program heif heist by harsh kvmescape by paulos php2shell by lcfr gitlab rces by joaxcar chrome full chain by moyix wordpress rce by hashkitten all largely thanks to openai daybreak giving researchers access to gpt 5.6 sol.
17
50
8
935
104,071
DestroyerX retweeted
Replying to @Hacker0x01
@Hacker0x01 I need to raise a serious concern about how three of my AT&T reports were handled. This is about inconsistent decisions, different root causes being grouped together, and a critical finding being denied independent evaluation. It started with #3923035, which had already been marked Resolved. I later discovered that the issue remained exploitable and submitted a NEW report, #4089210, documenting incomplete remediation, additional impact, and fresh proof of exploitation. The new report demonstrated confirmed token minting and role elevation, a capability that was not demonstrated in the original report. I followed H1's own guidance that regressions or bypasses of a fix must be submitted as new reports and reference the original. Yet the triager closed #4089210 as a duplicate and said: "AT&T usually requests a retest for submissions, I see that didn't happen with #3923035. Please report insufficient mitigation within the original report." How is that a reasonable basis for closing it? Whether AT&T requested a retest was outside my control. The original report had already been marked Resolved, and I followed the stated procedure by submitting a new report with fresh evidence. What happened next makes this even more confusing: the triager reopened #3923035, changed its status from Resolved back to Triaged, and instructed me to put the contents of the new report into the original. How can a new report demonstrating additional capabilities be closed as a duplicate, only for the already-resolved report to be reopened and moved back to Triaged to absorb those findings? Why instruct researchers to submit regressions as new reports if following that procedure results in the new report being closed and its contents moved into the original? Two other reports were also closed as duplicates with the instruction: "Please keep these contained in the same report." These reports have different root causes and separate technical evidence. To be clear, I'm not arguing that every affected endpoint deserves a separate report. I'm arguing that findings with genuinely different root causes should not be classified as duplicates without evaluating their technical differences and independent impact. I have submitted three mediation requests seeking a fair and independent review of these decisions: • #681596 • #681806 • #681807 I'm asking @Hacker0x01 to review all three closures, examine the technical basis for each duplicate classification, and reopen the reports where the evidence supports independent findings. I respect the triage process, but researchers also deserve consistent decisions and technically justified explanations. I trust @Hacker0x01 to review these cases fairly. I'm not asking for special treatment. I'm asking for a fair, independent review based on the evidence and the procedures HackerOne has communicated.
4
2
46
2,537