We now ban every reporter Instantly who submits reports we deem AI slop. A threshold has been reached. We are effectively being DDoSed. If we could, we would charge them for this waste of our time.
We still have not seen a single valid security report done with AI help.
~ Daniel Stenberg
Source [2025]-–
For those of you who don’t want to click into linked in, https://hackerone.com/reports/3125832 is the latest example of a invalid curl report
Source: https://news.ycombinator.com/item?id=43907751 [2025-05-06]
AI might be useful to find some bugs that might otherwise have been missed, but you still need to do the manual work to make sure it’s actually valid and produce a proof of concept.
Unfortunately, most of these sloppers don’t have the skills to validate the work.
You know those bug reports where the user somehow didn’t see the huge bug report right on the front page with 100 comments, pinned to the top of the issues page, and they duplicated it? Where they didn’t provide a log or a stack trace, or even their system specs? The kind of report which caused the developers to implement a massive issue template that the user just ignored?
We automated that 😎
That template? — Filled with garbage.
That stack trace? — Contains methods that don’t actually exist.
It’s not debugging, it’s deblowmyfuckingbrainsout.
Hey, someone with experience.




