<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>BountyBench: Dollar Impact of AI Agent Attackers and Defenders on Real-World Cybersecurity Systems · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2505.15216/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2505.15216/feed.xml" rel="self" type="application/rss+xml" /><item><title>BountyBench: Dollar Impact of AI Agent Attackers and Defenders on Real-World Cybersecurity Systems — mentioned by dudeinhawaii</title><link>https://news.ycombinator.com/item?id=44742451</link><guid isPermaLink="false">urn:hackerpapers:mention:2505.15216:44742451</guid><pubDate>Thu, 31 Jul 2025 04:56:21 GMT</pubDate><description>&lt;p&gt;Everyone is slamming you but the reality is that you could use AI models + a competent developer or security engineer to _very_ quickly shore up the entire codebase and fix every single hole -- getting it to a place where it&amp;#x27;s comparable with everything else out there. It&amp;#x27;s really not that hard (and there is already a bit of research around the defensive coding capabilities of tools like Codex and Claude Code)[1]. I have personally taken this approach with web dev, granted I&amp;#x27;m a very senior developer. First, develop features, then ask a larger/smarter model (o3, o3-pro, gemini-2.5 pro) to…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2505.15216/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
