Zero to Calc in Six Days: Inside XBOW's Chrome Full Chain
ollin
33 points
11 comments
October 13, 2026
Related Discussions
Found 5 related stories in 115.2ms across 9,386 title embeddings via pgvector HNSW
- Show HN: Watching browser fingerprinting calls via Chromium's Blink layer brnbs · 11 pts · August 10, 2026 · 47% similar
- Chrome's Breaking and Entering ingve · 25 pts · July 24, 2026 · 46% similar
- Which tools do Claude, Codex and Cursor choose? We measured 17k runs to find out screm · 158 pts · September 03, 2026 · 45% similar
- Half a Second – a book about the XZ backdoor zvr · 44 pts · July 19, 2026 · 44% similar
- Launch HN: Bullet (YC S26) – A Faster Coding Agent adi1 · 93 pts · August 13, 2026 · 43% similar
Discussion Highlights (4 comments)
ollin
This is a technical companion post to https://xbow.com/blog/xbow-built-a-chrome-full-chain-exploit
whiplash25
Anyone else confused with the timeline? Is it actually no bugs to working full chain in 6 days? 1. CEO announces goal in January. 2. Team took 2 months on first working full chain. 3. In August, they swap out 1 bug in the chain with a new one, weaponize in 6 days. Weaponization of 1 bug costs $40K in 5.6 sol token spend. Is that it?
creata
Off-topic*: Can I even visit untrusted websites anymore? Firefox's security is probably far worse than Chrome's, and escaping the browser sandbox now seems accessible to way too many people. * Kind of on-topic given the last sentence of the article...
ibackstrom
xbow are clowns. prompting pentesters ahahahah