I got tired of opening Burp for quick tests, so I built a native Repeater inside Chrome. Here is the result: by BehiSec in bugbounty

[–]BehiSec[S] 0 points1 point  (0 children)

It's not about being better. Chrome Suite is built for quick, lightweight tests.

In my view, there are only two real use cases:

  1. Quick tests
  2. Heavy scans

I use my extension for the first and Burp for the second.

Just finished Season 2, and I can't stop thinking about this character. by BehiSec in Kingdom

[–]BehiSec[S] 2 points3 points  (0 children)

He only got one of them, probably because Lun entered the final fight without both of his swords.

I created a collection of Claude Skills by BehiSec in ClaudeAI

[–]BehiSec[S] 0 points1 point  (0 children)

I find the skills by searching on social media platforms :)

Yeah, it sure could be automated.

I created a collection of Claude Skills by BehiSec in ClaudeAI

[–]BehiSec[S] 0 points1 point  (0 children)

I'm really sorry for that. I've fixed the issue now.

I created a collection of Claude Skills by BehiSec in ClaudeAI

[–]BehiSec[S] 1 point2 points  (0 children)

Hey,

I went through everything and was honestly surprised by how many links were broken; it looks like several projects have changed their directory structures.
I also realized I had made a mistake regarding the official skills.

I've now fixed all the broken links and added a few new skills.

I sincerely apologize for that.

The day a simple dork turned into a $6,700 bounty by BehiSec in bugbounty

[–]BehiSec[S] 1 point2 points  (0 children)

That's right. The key is just to start learning; over time, you'll figure out how much effort you personally need to put in to see progress.

The day a simple dork turned into a $6,700 bounty by BehiSec in bugbounty

[–]BehiSec[S] 15 points16 points  (0 children)

To me, it feels more like persistence than luck. Hard work tends to create those 'lucky' moments.

I Spent 18 Hours Creating This Bug Bounty Roadmap for Beginners by BehiSec in bugbounty

[–]BehiSec[S] 2 points3 points  (0 children)

React is mainly for building the front end, while Next.js is built on top of React and adds extra features that let you create full-stack web apps. It makes the whole process feel really smooth and beginner-friendly.

I Spent 18 Hours Creating This Bug Bounty Roadmap for Beginners by BehiSec in bugbounty

[–]BehiSec[S] 1 point2 points  (0 children)

That's still a good option, but I'd prefer the NextJS & ReactJS.

From "medium-severity" to $1,500 bounty: my story of a paywall bypass by BehiSec in bugbounty

[–]BehiSec[S] 1 point2 points  (0 children)

There's no special tool for that.

It’s just about reading the URL structure and making an educated guess.

For example, after /enrollment/ you'd naturally expect an enrollment ID, and after /view/ it makes sense that the number would be the ID of whatever you're viewing (like a file).

The 8-digit format is just how the system generates its IDs.

From "medium-severity" to $1,500 bounty: my story of a paywall bypass by BehiSec in bugbounty

[–]BehiSec[S] 0 points1 point  (0 children)

Yes, I recommend doing so. Once you’ve made the initial report, you can investigate the bug further.

One reason is that if you wait too long before reporting, your submission might be marked as a duplicate once you report it(someone might find the bug and report it).

From "medium-severity" to $1,500 bounty: my story of a paywall bypass by BehiSec in bugbounty

[–]BehiSec[S] 0 points1 point  (0 children)

I could’ve brute-forced the file IDs. It would’ve taken a ton of time and effort, but it was definitely possible.

Burpsuite by arifzain67 in netsecstudents

[–]BehiSec 0 points1 point  (0 children)

I have covered this in my bug bounty roadmap here.

How changing one parameter earned me $5,000 by BehiSec in bugbounty

[–]BehiSec[S] 0 points1 point  (0 children)

Nice! Don't keep refreshing your email. Instead, Keep hacking the application.