A.fahimi (@af4himi) header
A.fahimi (@af4himi) profile picture

Bug Hunter. We Try Pwn The World!

Joined February 2019
Photo by A.fahimi (@af4himi)Photo by A.fahimi (@af4himi)Photo by A.fahimi (@af4himi)Photo by A.fahimi (@af4himi)Photo by A.fahimi (@af4himi)Photo by A.fahimi (@af4himi)Photo by A.fahimi (@af4himi)Photo by A.fahimi (@af4himi)Photo by A.fahimi (@af4himi)Photo by A.fahimi (@af4himi)
Nice day and nice Bug= Nice bounty :)))😎🤘💸 Yay, I was awarded a $3,000 bounty on @Hacker0x01 #TogetherWeHitHarder
15
7
314
Has anyone exploited php2shell? 🤔 I don't think so.🤷‍♂️ #php2shell
15
3
67
15,159
An API key in an APK can be limited, monitored, or designed for a public client. A production TLS private key has no reason to be there. One app shipped the encrypted key and the material needed to decrypt it. Once unpacked, the client contained the full credential used by the live service. Reward was $3,500. Mobile review should classify secrets by authority: - Public identifier. - Quota-bearing API key. - User-scoped token. - Shared signing secret. - Production private key. Do not report every random string as Critical. But when an app ships infrastructure identity, prove the exact certificate or signature relationship and treat it accordingly. . #BugBounty #CyberSecurity #TogetherWeHitHarder #ItTakesACrowd #Bugcrowd #Hackerone
10
8
243
8,124
after seeing the current state of HackerOne, I decided it was time to sit down and address the elephant in the room blog.teknogeek.io/posts/what…
23
181
21
825
160,908
A.fahimi retweeted
What the fu*ck ?? @Hacker0x01 You just keep banning top researchers from the platform for no real reason. Ever since @ksprague08 became CEO, we’ve seen this problem constantly top hackers getting banned left and right. We never saw this when Marten Mickos @martenmickos was in charge. At this rate, no one will trust HackerOne again.
I got permanently banned from @Hacker0x01. Account deleted. No explanation. Years of work gone overnight. Submission history, achievements, leaderboard ranks, every contribution I made to the security and crypto ecosystems through HackerOne. Wiped, like I was never there.
7
14
179
21,015
امیر کیانی فعال حوزه‌ی امنیت سایبری مدتیست در بازداشت است، صدای او باشیم. #امیرکیانی
1
19
1
114
4,180
Building and selling AI trained on researchers’ reports while closing researcher accounts without clear explanations? That’s not how you treat the community that built your platform. Transparency, consent, and respect for researchers are not optional. @Hacker0x01
Point-in-time pentests can’t keep up, while fully autonomous testing creates noise. The solution? HackerOne Agentic PTaaS pairs specially trained AI agents with elite human validation to deliver results based on real-world exploitability, not theory. This 50-second video shows you how it works.
1
62
3,697
you just need to find the right entry point 🔥 Still hunting, still learning — the journey continues. Deep recon always pays off🤓 #Bugbounty
15
2
279
8,229
reading Js >> found an endpoint file inclusion >> LFI >> RCE :D Write-up will be published after fix on: blog.voorivex.team #BugBounty
9
22
1
430
32,884
بچه هایی که باگ بانتی‌کارمیکنید سوال میکنید برای نقد کردن بانتیامون چیکارکنیم امیر @Amir0x01 کارش‌ خیلی درسته آی‌دی تلگرامشم میزارم کمکی خواستید براتون اوکی میکنه t.me/Offensive
6
2
56
7,534
HackerOne is banning accounts without any clear reason. My account, with 2 years of work and $5000 left in bounties, was banned for nothing. It’s obvious they just want to take hackers’ rights. Shame on HackerOne." These actions by HackerOne are purely business-driven @Hacker0x01
I’ve been hunting on H1 for almost 3 years, ranked #18 in 2025, have always tried to contribute positively to the hacker community. I’ve earned around $500k in bounties and was on the road to $1M. Yet I don’t even have HSM, and I feel I haven’t been recognized as I should 1/4
7
12
2
227
17,881
A.fahimi retweeted
Yesterday it was me and @GodfatherOrwa. Today, HackerOne banned @YShahinzadeh — one of the most talented hackers on the platform. Tomorrow it could be any of us… unless you’re a big content creator with a huge following. HackerOne grew because of hackers. We deserve to be treated with respect, not sidelined. The community that built the platform deserves better.
9
16
2
270
31,015
I took a little break from bug bounty. But I’m back now — and made $13,850 in just one month. Guess the bugs missed me 🐞💰 Huge thanks to @Bugcrowd and @yeswehack for the support and awesome platforms 🙌 #Bugbounty #ItTakesACrowd
17
11
374
18,482
A.fahimi retweeted
Replying to @LBank_Exchange
@LBank_Exchange TFy77c1qsBwjjo1gDfthNxVPjcnGy6Vxa4 I hope you get this message. I would like to inform you that the hacker's wallet address has been exposed and unauthorized transactions have been sent to your exchange. If possible, please block these transactions and help this user resolve this issue. Unfortunately, I was unable to find any direct contact information for your team. Thank you for your prompt attention to this issue.
This quoted post is unavailable.
27
6
1
40
6,706
Excited to share that I’ve made it to the Top 25 ranking researchers on @Bugcrowd this month! 🎉 It’s been a journey full of challenges and learning, and there’s still more to come. Big thanks to the amazing security community for the support and motivation! 🔥 #BugBounty
9
2
165
9,058
In the last month of the year, I earned $20k bounty and reached 6th P1-P2 leaderboard in October. I had great moments this year in the @Bugcrowd platform.
15
3
227
14,194
This month I earned $7,500 bounty and reached the 28th rank of P1 Warrior in @Bugcrowd , Only with 7 hours of work per day. #BugBounty
20
5
269
18,465
Good Friday😎🤙 Just got a reward for a critical vulnerability submitted on @yeswehack -- SQL Injection (CWE-89). #YesWeRHackers
6
1
110
7,568
A.fahimi retweeted
The damage of VDP programs and their Incentivization is far greater than giving some hunters "points" for farming none-bugs that they can later boast on their CV's, I believe it might actually ruin Bug Bounty platforms in the near future, Let's explore the facts 📜 So VDP's, as most people refer to "See something, Say something" type of programs, have gone out of control on most bug bounty platforms, the only one who took significant step against the phenomena is @Bugcrowd about ~2 years ago, completely dropping VDP points and truly making them live to their actual purpose. @Hacker0x01 said at 2021 that they will be pushing to that direction, without anything meaningful so far. So, why is it so bad? 1. "Worsening experience for Bug Bounty Hunters and Paid Bug Bounty Programs" IMO, this is the most concerning aspect of VDP's and when platforms double-down on them - major platform resources are invested in triaging, communicating and managing VDP "Points Only" programs. In 2024 alone, there were between ~3,500 to 5,000 VALID VDP submissions on @HackerOne (Had to do an estimate by looking at the top VDP programs). With the signal/noise ratio on these public programs, and by looking on top VDP programs "last 90 days reports" statistics, we can see that there were around ~15,000 to 20,000 submissions to VDP programs in 2024, those are being handled by the same Triage teams and same queues that Bug Bounty Programs who pay money to researchers are, thats probably more or if not the same amount of total submissions to all paid BBP programs on the platform, which are ~x5/x6 in numbers. This leads to: A. Significant Triage Burn-Out, Triage teams go through hundreds of invalid reports, or hundreds of same-issue submissions that are being triaged individually, exhausting the triage experience on paid bug bounty programs, in which the reports usually are more complex and require better in-depth overview. B. Absurd triage times - critical reports to CLEAR / BBP programs who are not being looked for over a week, programs miss out on their critical bugs while they are exploitable, hunters miss out on their bugs being paid. C. Almost none-existing communications on submissions, enormous triage queues and VDP overheads leads to the fact that its super challenging and hard to get a feedback on existing submitted reports, or having a dialogue with triage teams, the situation today is usually leaving a comment and "praying" triage member will respond. D. Mediations are completely dead - the significant number of submissions, often from new-comers could lead to mediation requests on none issues, the same queue today exists for paid programs mediations and points only programs, again - affecting the portion of researchers who actually contribute the most value to platforms, finding valid vulnerabilities on paid programs. 2. "Free Labor" / "Can only find bugs on VDPs" The most obvious thing that comes to mind is the fact that people "work" for free helping multi-billion companies bolster their security, VDP's can be great training ground for new-comers, but the reality today is that >90% of the people who report to VDP programs do so solely to boost their reputation and platform standings because its easier to find bugs there, the programs don't care if you spam ~200 reports on same XSS on same Endpoint and you fake out parameters, and so on. Think about it - if you managed to find XSS on a VDP via redirect_uri on login page, you most certainly could have found it on a BBP, but you missed it because you were focused on the VDP while the BBP introduced the issue. Today, there are ~200 VDPs on @Hacker0x01 133 VDPs on @Bugcrowd (I do like that they have completely separated view on the platform) 3. Leaderboards are not trust-worthy #BugBounty is well gamified space, we all push ourselves the extra-mile to do well and beat our colleagues in the rankings, however VDP's made the state of public leaderboards so unstable and not trust-worthy that they are not even taken into context when determining "top hackers" for events invites, or so on. Within Q2 (Apr 1st to Apr 16th) we have 8 VDP-Only Hunters on HackerOne's Top 100 leaderboard, including the #1 hacker in the world. While on the actual leaderboard you do gain some advantage if you hunt on BBPs, as you get some spare change of reputation points when you are awarded a bounty, the sub-leaderboards as "Highest Critical Reputation" do not distinguish between VDPs and BBPs at at all, it's straight 7 reputation points for any triaged High / Crit, whether a free one / one that got $200k bounty. This means that in Q2 3 of the Top 5 Most Critical Hackers in the world are VDP-Only hackers, and ~20 out of the Top 100 on the 2024 Leaderboard. Eventually, this leads to actually debating whether we should focus on VDPs to improve our rankings on platforms leaderboards. 4. "Same Scope VDP/BBP Scams" The standardization of having public incentivized VDP accompanied to a private BBP is the worst thing you can do as a program. A. Programs will tend to think that the "winning model" would be having main application in scope for private BBP, and have public VDP for all their "wildcards", that's a huge mistake if your company are actually looking in preventing their next breach, so many critical vulnerabilities that can cause to a complete incident in matter of minutes will remain unattended for weeks, no-one would bother to give you an actual time sensitive submission on a program without monetary rewards. B. Sometimes, it's just straight up a scam - same scopes for both programs, researchers submit to VDP and lose on money. Having an unincentivized responsible disclosure policy submission form on your website and a private BBP is more than okay, thats actually a perfect use-case, have your own set of researchers and accept in-coming reports as "see something - say something" from the crowd, I bet that if you'll find someone reporting super critical submission, It'll probably lead to a private program invite - unlike when having a "Points Reward" program on a platform already, that you feel the "award" was given already. Solution 💡 Well, if you made it so far - there is a solution, and it's one that will make all parties happy. The formula: 1. Remove VDP Points from platforms and Leaderboards. 2. VDP Contribution Recognition - Whenever a researcher submits a valid report to a VDP, display the company logo on his profile, and auto-generate a "Thank You" letter in which he could use in his CV. 3. Auto-Invite researchers who discover a valid bug on private BBP scope in a pubic VDP. 4. No Mediations on VDPs. 5. Sales pitches should specify that companies won't be getting time-sensitive issues on VDPs, pushing them to create BBPs. 6. Kill Private VDPs. Going through the formula, VDP hunters will still receive valuable recognition for their VDP submissions, BBP hunters will enjoy a clean leaderboard who pushes for paid program submissions, Triage teams will go through way less overload, Mediations will start working again, Less VDP's => More BBP's because companies eventually want to be secured, more BBP's => More Money to platforms. Disclaimer: everything I've wrote here is based on my thoughts and analysis. Thoughts? Is there any advantage to any party for awarding points on VDP's? am I hallucinating? #BugBounty – at Israel
60
154
39
703
191,275
A.fahimi retweeted
More and more BBPs programs leaving/closing at a crazy rate New VDPs every month Almost 300 Reports in less than a week for this new VDP We are doomed.
30
12
5
227
52,392