Skip to content
0:00 / 0:00

#curl#danielstenberg#aislop

AI slop attacks on the curl project - Daniel Stenberg

Daniel Stenberg

11K subscribers • 1 video on Hallway

YouTube
  • Recommended by 1 person: 1 on Hacker News.
  • Presented by Daniel Stenberg, creator of curl
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

46K views1 year ago1 recommendation

SecurityTools and practiceOpen sourceWeb and application securityTransformers and LLMs

Daniel Stenberg discusses the influx of low-quality, AI-generated security reports targeting curl and the challenges they pose for open-source maintainers.

Keynote at the FrOSCon 2025 conference, August 16, in Bonn Germany by Daniel Stenberg.

Why it's here

1 person recommends this

What people say. Recommended as a firsthand account of how AI-generated noise and bogus security reports impact open-source maintainers.

a235on Hacker News • Recommends

On “You did this with an AI and you do not understand what you're doing here”

Maintainer or curl gave recently a talk on AI slop in security reports, showing this and other examples: link to this video -- AI slop attacks on the curl project - Daniel Stenberg. Keynote at the FrOSCon 2025 conference, August 16, in Bonn Germany by Daniel Stenberg. Plus, linked above, his blogpost on the same subject link

shooon Hacker News • Mentions

On “You did this with an AI and you do not understand what you're doing here”

last month curl developer Daniel Stenberg gave a talk "AI slop attacks on the curl project" : link to this video

jonchurch_on Hacker News • Mentions

On “Ask HN: How to deal with long vibe-coded PRs?”

Daniel Stenberg of curl gave a talk about some of what theyve been experiencing, mostly on the security beg bounty side. A bit hyperbolic, and his opinion is clear from the title, but I think a lot of maintainers feel similarly. “AI Slop attacks on the curl project” link to this video

jraphon Hacker News • Mentions

On “We will ban you and ridicule you in public if you waste our time on crap reports”

> the problem at hand is one of high asymmetry between the low effort to submit vs the high effort to review Hence the threat to shame publicly I suppose. Actually, Daniel Stenberg previously responded to this proposal the same way as me 1 (and maybe would still do). Coincidentally, I was reading your answer at about the same time as this part of the talk. 1 link to this video (via link )

latexron Hacker News • Mentions

On “We will ban you and ridicule you in public if you waste our time on crap reports”

A lot of solutions have been suggested over the past few months, including those. They have drawbacks and it’s not how they want to run the project. link to this video