Claude Opus wrote a Chrome exploit for $2,283
What happened
In a blog post on Wednesday, Mohan Pedhapati (s1r1us), CTO of Hacktron, described how he used Opus 4. 6 to create a full exploit chain targeting the V8 JavaScript engine in Chrome 138, which is bundled into current versions of Discord. This matters for IT, Telecom & Cyber because fresh price movement and input-cost detail should reset bid assumptions, breach response slas, and negotiation guardrails with 4.6, 4.7, 138 as the clearest commercial anchors; expect renewal uplift asks
Buyer takeaway
For IT, Telecom & Cyber, treat this as a cost-boundary signal rather than just a headline; buyer assumptions may need refreshing before the next quote or award decision
Cost / money
Use this to refresh should-cost views and challenge any fast repricing. Keep the read-through directional unless the source itself provides hard commercial numbers
Supplier / commercial
Suppliers with fresh cost justification may push harder on reopeners, indexation, shorter quote validity, or pass-through language. Buyers should separate real drivers from negotiation posture
Safety / operations
The operational risk is indirect: tight budgets or repricing battles often reappear later as reduced slack, substitutions, or execution compromises that buyers then have to manage
What to watch
Watch for shorter quote validity, reopeners, pass-through requests, or attempts to reset pricing on the back of weak evidence
Key facts
- In a blog post on Wednesday, Mohan Pedhapati (s1r1us), CTO of Hacktron, described how he used
- 6 to create a full exploit chain targeting the V8 JavaScript engine in Chrome 138, which is b
- "The V8 [out of bounds error] we used was from Chrome 146, the same version Anthropic's own C
- 3 billion tokens, $2,283 in API costs, and about ~20 hours of me unsticking it from dead ends
