@Hacker0x01 and @Bugcrowd should consider requiring a video Proof of Concept with every report. It would help confirm that the researcher actually reproduced the issue rather than relying solely on AI, while also providing clear evidence of the finding.
We were made aware of concerns regarding the visibility of chat messages and code on Lovable projects with public visibility settings.
To be clear: We did not suffer a data breach.
Our documentation of what “public” implies was unclear, and that’s a failure on us.
Specifically for public projects, chat messages used to be visible — this is now no longer possible.
When it comes to code of public projects: That is intentional behavior. We have experimented with different UX for how the build history is surfaced on public projects, but the core behavior has been consistent and by design.
Importantly, for enterprise customers, being able to set visibility to public for new projects has been disabled since May 25, 2025.
@Masonhck3571 I always send a resumed report focusing on important things. I don't care about remediation, or a lot of blabla in impact. the most important for me is "steps to reproduce" .
@naysser336283 @intigriti I understand Those are PayPal charges fees, but the sender decides who covers them. On HackerOne and most clients, fees are covered so the full amount is received. At least there should be clear notice if they’ll be deducted from the payout.
No, the sender decides who bears the fee. In this case, Intigriti chose to pass the fees to the receiver.
On other platforms like HackerOne, they choose to cover those fees so the researcher receives the full bounty.
As for the PayPal option and not a bank wire, I used it because I needed to send a portion to a collaborator.
Is it normal that Intigriti makes the researcher pay the fees and not get the full bounty? The support answer was weird since PayPal clearly shows that the receiver is the one being deducted for the fees. This was the case for me and @naysser336283 in @intigriti, while HackerOne payouts via PayPal are normal and fully received.
@craigzLiszt This is called mocking Islam. You're already out of it now.
9:64 They hypocrites are apprehensive lest a surah be revealed about them, informing them of what is in their hearts. Say, "Mock [as you wish]; indeed, Allah will expose that which you fear
Ember is the best Bugcrowd triager for non-P1s. He usually gets it right on the first try,if he asks something it’s usually important.
For P1s,Tal used to be the best, but now he seems more rushed, "this isn’t P1, next time N/A." Now Jack seems to be the best when it comes to P1s
I also noticed in @Bugcrowd that some triagers comment only not to reproduce, but only to win time. I mean, you put a clear answer and then he asks the same thing or something that's clear. Bugcrowd triagers are very slow, except when triaging P1 reports.
Hunting on Bugcrowd be like :
- 1 week gaps between replies = late triage
- No manual severity? Found a vulnerability that is P2 or P1 but impact is not in VRT category? congratulations you cannot select severity and now your report will take like 1 week to be seen
@AkashHamal0x01 Also, making IDORs leading to PII a P3 was the worst thing Bugcrowd ever did. You find huge PII data with juicy info, and based on the VRT, it's a P3.