Pinned Tweet
Recently I don't tweet much, but today has been a beautiful day that made me feel better after some other disappointments:
9th in Spain ๐ช๐ธ and a great impact!
A year or so ago this was unthinkable for me ๐
Thanks #BugBounty
๐ต๐๐๐ | jotita3 retweeted
๐ Your next security finding could earn you double the rewards.
@Deriv has launched a two-week bug bounty campaign on HackerOne, offering 2ร bounty rewards for eligible Medium, High, and Critical vulnerabilities.
Running from November 10โ24, the campaign gives security researchers an opportunity to put their skills to work, uncover meaningful vulnerabilities, and help strengthen Deriv's security.
Ready to take on the challenge? ๐ฏ
Explore the campaign and submit your findings: bit.ly/4fp9Pnz
๐ต๐๐๐ | jotita3 retweeted
โข Triage is extremely slow or practically nonexistent: This is something affecting all platforms, and from what I understand, Bugcrowd has recently expanded its triage team, which seems like a positive step. It's also true that, since my account is "new", I probably don't get much priority in the queue. But even so, the delays are honestly ridiculous.
โข Reports get closed with canned responses such as:
โฃ "We were unable to reproduce your issue" โ OK, fair enough, but can we discuss what went wrong? Why immediately close it as N/A and call it a day?
โฃ "If you still believe that this issue is valid after your review, please create a new submission" โ So the solution is to keep flooding the triage queue instead of keeping the entire discussion in a single report? Am I supposed to submit the same issue X times until I finally get a triager who can reproduce it?
โฃ (This one is probably my favorite lol) "This is all theoretical with no actual valid proof of concept as this submission only contains text-based claims" โ What exactly do you mean by "theoretical" and "no PoC"? Isn't source code, raw HTTP requests, and step-by-step reproduction instructions a PoC? Does the vulnerability suddenly cease to exist? Or, put differently, if I fill my report with screenshots and pretty decorations, does that suddenly make me a super hacker? (This is a made-up example: Do I really need to attach a screenshot of alert(1) so you don't have to test the vulnerable request that triggers that same alert(1)?)
โข I open blockers (= requests for Bugcrowd's intervention, somewhat similar to mediation on H1) and, of course, nobody from Bugcrowd responds.
Examples
โข In one report, the company's own staff opened a blocker requesting Bugcrowd to assess the impact. Since Bugcrowd never responded, the company had to handle the entire report and pay the bounty without any assistance from the platform (which, I assume, they're paying for...). And here's the cherry on top: once the company had already paid, the vulnerability had been fixed, and everything was resolved, Bugcrowd finally showed up!!! And what for, you might ask? Well, to update the report status and award me some internet points (Very useful!!! Please note the sarcasm.)
โข I gained access to a company's Dropbox through a leaked API key exposed on a subdomain associated with one of its programs. A pretty serious impact, in my opinion, and certainly not the kind of access you'd want a real attacker to have. Well, the solution was simple: N/A. Because, of course, since the subdomain wasn't explicitly listed in scope, we should apparently understand (sarcasm again) that we can't act ethically and report unauthorized access to a service because, oops, I happened to inspect the source code of an OOS subdomain... (As if the root issue in my report were a vulnerability in that subdomain rather than an API key leaked through whatever means.)
2/4 ๐งต
๐ต๐๐๐ | jotita3 retweeted
I also want to share my experience with @Bugcrowd, since it seems I'm not the only one:
Initial context
Since incorporating AI into my workflow, I've been able to significantly increase the number of vulnerabilities I discover and report while spending roughly the same amount of time on Bug Bounty as before.
Instead of simply doubling my submissions to HackerOne, I wanted to diversify and give Bugcrowd a try. It was a platform I was barely familiar with (in terms of how they operate, what programs they offer, etc.), but I found it interesting because of the well-known companies running programs there and bounty tables comparable to those on H1
My experience with the platform
Since August this year, I've been submitting reports with genuine enthusiasm and confidence about starting my journey here. Unfortunately, the experience has been nowhere near what I imagined.
Here are my main issues and criticisms:
1/4 ๐งต
Triaging experience at @Bugcrowd is extremely bad, even the valid demonstrated findings with POC and high - critical impacts are being marked N/A with templated comments.
I also want to share my experience with @Bugcrowd, since it seems I'm not the only one:
Initial context
Since incorporating AI into my workflow, I've been able to significantly increase the number of vulnerabilities I discover and report while spending roughly the same amount of time on Bug Bounty as before.
Instead of simply doubling my submissions to HackerOne, I wanted to diversify and give Bugcrowd a try. It was a platform I was barely familiar with (in terms of how they operate, what programs they offer, etc.), but I found it interesting because of the well-known companies running programs there and bounty tables comparable to those on H1
My experience with the platform
Since August this year, I've been submitting reports with genuine enthusiasm and confidence about starting my journey here. Unfortunately, the experience has been nowhere near what I imagined.
Here are my main issues and criticisms:
1/4 ๐งต
Triaging experience at @Bugcrowd is extremely bad, even the valid demonstrated findings with POC and high - critical impacts are being marked N/A with templated comments.
Conclusions based on my own experience and small sample size
โข Poor management of report volume, especially given the current state of vulnerability research.
โข Overwhelmed triagers whose easiest option seems to be closing reports, trusting that the researcher will submit a new one that better matches whatever the triager expects, requiring the least possible effort on their part. I fully understand that researchers should make the triager's job easier, but that's very different from expecting every vulnerability to be a one-click or one-step exploit so the triager can just chill.
โข The meaning of N/A seems completely distorted compared to other platforms. How is it possible that there's no room for technical discussion within reports and that potentially valid bugs are being lost because N/A is being handed out as if those reports were spam?
โข Canned responses with no real value or transparency. It doesn't matter whether you submit a P1/P2 that, for whatever reason, the triager can't reproduce. In practice, you'll receive the same N/A as someone reporting a missing security header lol.
โข A terrible initial experience due to submission limits and little to no prioritization in the triage queue simply because you're "new". And I understand the reasoning behind that, but shouldn't we be taking researchers' track records on other platforms into account? If I have almost 2.5K reputation points on HackerOne and a historical signal above 6.3, shouldn't that count for something when establishing credibility on your platform? Instead, you're actively pushing me away from it.
3/4 ๐งต
1
12
887
Clarifications
โข I'm not trying to single anyone out. There are better and worse professionals everywhere, as in any industry.
โข I'm not questioning the triagers' level of expertise or technical knowledge.
โข I believe the real issue lies with Bugcrowd's management and leadership for neglecting both their customers and researchers.
โข I don't wish the platform any harm. I genuinely want what's best for the ecosystem and for everyone involved to benefit. A win-win for all.
4/4 ๐งต
1
10
785
Incredible bugs still waiting to be discovered, and companies already running out of bounty budgets...
What a crazy time to be alive in the AI era. But today, I'm happy!
#bugbounty #hackerone
๐กTip:
It was a bit more complex, but take a look at this lab to get a basic understanding ๐ portswigger.net/web-securityโฆ
Done! Now letโs go for 100!๐
#bugbounty #hackerone
I've reached 20 thanks from companies on @Hacker0x01 ! For many, it may be a small achievement, but for me, it's really exciting!
On to 50๐
2
20
635
I see people doing really well on @Bugcrowd, while my experience has been absolutely horrible. Am I the only one?
1
152
๐ต๐๐๐ | jotita3 retweeted
Replying to @_godiego__
Itโs a numbers game.
If my AI slop bot submits a few thousand submissions, at least one or two should be valid and pay out.
Overall, Iโm not having my best day today... and when Iโm having a bad day, I tend to come here to vent... sorry lol. Let me tell you whatโs going on:
The thing is, my income and the number of reports I submit have improved massively since AI became part of our lives. And yet, I donโt feel happier, quite the opposite.
I feel more like a slave to it. Like weโre just โmanufacturingโ money now. Like thereโs no longer much point in enjoying the technical side of things. I see newcomers achieving in days what took me months or even years of effort to accomplish. Now it feels like weโre all competing on equal terms, but without necessarily having the same level of knowledge or experience.
I also feel like all of this could disappear from one day to the next, or that I have to keep farming more and more every single day because otherwise the person next to me will sweep everything up and take the opportunities before I do.
And then thereโs seeing all these unfair flexes on social media, which inevitably creates FOMO, especially when they come from people who sometimes seem to have very little actual knowledge...
Iโm not enjoying the moment... I donโt know how to deal with this situation. AI has messed with my dopamine.
I wasnโt sure whether I was going to report it... sometimes your favorite report gets closed, and other times an unexpected one makes your morning. Nice program!
Thatโs just how bug bounty goes ๐
Have a great day everyone!
๐ต๐๐๐ | jotita3 retweeted
Maรฑana Bugs & Talks - #4 @moblig_
Video: youtu.be/C6J_fR32pcc?si=TfcAโฆ
#bugbounty #podcast #ciberseguridad
Seguimos desvelando el cartel del #BugSummit y este nombre viene con una charla que promete dar mucho que hablar.
El prรณximo 20 de junio subirรก al escenario de La Nave Juan Antonio Rodrรญguez Bautista @sec_jota, mรกs conocido como Jotita3, una de las caras mรกs reconocidas del panorama nacional del Bug Bounty y alguien que ha demostrado, una y otra vez, cรณmo pequeรฑos fallos pueden convertirse en grandes compromisos de seguridad.
En su ponencia, "๐๐ฐ๐ฐ๐ผ๐๐ป๐ ๐ง๐ฎ๐ธ๐ฒ๐ผ๐๐ฒ๐ฟ: ๐๐น ๐ฎ๐ฟ๐๐ฒ ๐ฑ๐ฒ ๐ฐ๐ผ๐ป๐๐ฒ๐ฟ๐๐ถ๐ฟ ๐ฏ๐๐ด๐ ๐ฒ๐ป ๐ฐ๐๐ฒ๐ป๐๐ฎ๐ ๐ฟ๐ผ๐ฏ๐ฎ๐ฑ๐ฎ๐", compartirรก casos reales de Bug Bounty donde vulnerabilidades descubiertas en entornos reales terminaron derivando en compromisos completos de cuentas.
Analizaremos fallos directos y escenarios mรกs elaborados que permitieron tomar el control de cuentas, entendiendo el impacto real, la causa raรญz detrรกs de cada hallazgo y las lecciones aprendidas durante el proceso.
Casos reales, metodologรญas prรกcticas y la visiรณn de alguien que ha vivido este tipo de hallazgos desde dentro.
Serรก, sin duda, una de esas charlas imprescindibles para cualquiera que quiera entender cรณmo un bug aparentemente inofensivo puede acabar convirtiรฉndose en un Account Takeover.
Si quieres aprender de quienes viven el hacking en primera lรญnea, la cita es el prรณximo 20 de junio.
Consigue tu entrada aquรญ ๐secur0.com/es/feria-de-empleโฆ
#BugSummit2026 #BugBounty #AccountTakeover #Ciberseguridad #EthicalHacking #TechConference




















