Claude Opus wrote a Chrome exploit for $2,283

Mohansrk 18 points 11 comments April 18, 2026
www.theregister.com · View on Hacker News

Discussion Highlights (4 comments)

pingou

I know most people here hate that, but I think this makes a much stronger case for security by obscurity (not releasing the source code) in these changing times. Of course security by obscurity by itself is by no mean sufficient.

localhoster

> "A week of back and forth, 2.3 billion tokens, $2,283 in API costs, and about ~20 hours of me unsticking it from dead ends. It popped calc." Corrent me if I'm wrong, I'm not a security researcher, but 20 hours, a week of work, 2283$ spent and over 2 trillion tokens, is not very 10x-ing as we were promised. Especially if you take into account that the guy is at least half capable for this take. I dunno

ofjcihen

This has been what I’ve been screaming from the rooftops for a while, that these models can already do this. Go read the devs actual blog though. This is more a statement on patch lag than anything else. In my mind that’s much more important than “zomg zero days!!!”

jdndnejdn

A security researcher instructed an LLM to write an exploit for a know bug fixed in an already published release Not really impressive

Semantic search powered by Rivestack pgvector
4,930 stories · 46,452 chunks indexed