Live
Breaking
40m ago Hardware & Chips Colorful K16: 128GB RAM AMD Laptop Hits $5,960 [2026] 1h ago AI & Machine Learning Abacus.AI Smaug Models Cut Agent Costs 100x [2026] 3h ago Cybersecurity Russia’s Claude-Built Drones: 9 Accounts Banned [2026] 4h ago Gaming Diablo 4 Hits Switch 2 Sept. 15, Bundles 2 Expansions [2026] 5h ago Hardware & Chips Intel Xeon 6+ Hits 288 Cores on 18A, Beats Epyc 30% [2026] 5h ago Hardware & Chips Intel, AMD Drop 4.2% as Nvidia Unveils PC Chip [2026] 6h ago Cloud Computing 9,300 Leaked AWS Keys Still Active, 768 Grant Admin [2026] 7h ago Cybersecurity Conti Hacker Lytvynenko Gets 4 Years, Faced 20 [2026] 8h ago Esports Uninstall Valorant, Keep Vanguard: 12 Steps [2026] 9h ago Gaming COD’s Anti-Cheat Boss Explains Bans, 1 Year In [2026] 10h ago Cryptocurrency Run a Bitcoin Lightning Node: LND Setup in 12 Steps [2026] 11h ago AI & Machine Learning Meta Preps Muse Custom Voices as App Hits 83K [2026] 12h ago Provably Fair Girls Frontline 2 Pity Odds: 0.6% Rate, $396 Worst Case [2026] 13h ago Gaming PlayStation’s Fairgame$ Leaks Under 3rd Code Name [2026] 40m ago Hardware & Chips Colorful K16: 128GB RAM AMD Laptop Hits $5,960 [2026] 1h ago AI & Machine Learning Abacus.AI Smaug Models Cut Agent Costs 100x [2026] 3h ago Cybersecurity Russia’s Claude-Built Drones: 9 Accounts Banned [2026] 4h ago Gaming Diablo 4 Hits Switch 2 Sept. 15, Bundles 2 Expansions [2026] 5h ago Hardware & Chips Intel Xeon 6+ Hits 288 Cores on 18A, Beats Epyc 30% [2026] 5h ago Hardware & Chips Intel, AMD Drop 4.2% as Nvidia Unveils PC Chip [2026] 6h ago Cloud Computing 9,300 Leaked AWS Keys Still Active, 768 Grant Admin [2026] 7h ago Cybersecurity Conti Hacker Lytvynenko Gets 4 Years, Faced 20 [2026] 8h ago Esports Uninstall Valorant, Keep Vanguard: 12 Steps [2026] 9h ago Gaming COD’s Anti-Cheat Boss Explains Bans, 1 Year In [2026] 10h ago Cryptocurrency Run a Bitcoin Lightning Node: LND Setup in 12 Steps [2026] 11h ago AI & Machine Learning Meta Preps Muse Custom Voices as App Hits 83K [2026] 12h ago Provably Fair Girls Frontline 2 Pity Odds: 0.6% Rate, $396 Worst Case [2026] 13h ago Gaming PlayStation’s Fairgame$ Leaks Under 3rd Code Name [2026]
NewsroomLive
Today20 new
Archive710 stories
Last filed40m ago
Languages10
UTC02:40:07
Top Story Hardware & Chips

Colorful K16: 128GB RAM AMD Laptop Hits $5,960 [2026]

Colorful has confirmed a 16-inch laptop built around AMD's Ryzen AI Max+ 395 chip, and the spec sheet is the kind that makes PC builders do a double take: up to 128GB of unified LPDDR5X memory,…

40m ago  ·  Sep 13, 2026 Read the brief

The Desks

// editorial departments

Latest

// fresh from the editors

More from the desks

// keep digging
// about

About Shattered.io

This domain has been home to the SHAttered SHA-1 collision project since 2017, and is now a hub for cryptography, security and privacy reporting. The full origin story of the project, the two proof PDFs and the research credits live below.

The SHAttered project — origin, proof files and research credits

On 23 February 2017, researchers at CWI Amsterdam and Google showed the world the first real collision for the SHA-1 hash function. The project was called SHAttered, and this domain has been its home ever since. The two files that prove the break are still here to download.

What a collision actually is

A cryptographic hash takes any file and returns a short fixed-length fingerprint. The promise is simple: change a single bit of the file and the fingerprint changes too, and no two different files should ever share one. A collision breaks that promise. It is a pair of distinct inputs that produce the exact same hash. For a function used to sign software, certificates and documents, a collision is not a curiosity. It is a crack in the foundation.

What SHAttered produced

The team did not just argue that SHA-1 was weak on paper. They built the evidence. Two PDF files, visibly different and carrying different content, share one identical SHA-1 value: 38762cf7f55934b34d179ae6a4c80cadccbb7f0a. Run either file through SHA-1 and the answer matches. Run them through SHA-256 and the answer differs, which is how anyone can confirm they are genuinely two separate files.

What the attack cost

The break was expensive, and that was part of the point. Producing the collision took roughly nine quintillion SHA-1 computations, the work of about 6,500 CPU-years and 110 GPU-years run in parallel. That scale kept the attack out of reach for a casual attacker in 2017, yet it ran thousands of times faster than trying every possibility by brute force. The direction of travel was clear: the cost would only fall.

Why SHA-1 had to retire

Once a working collision exists, trust in a hash erodes quickly. Within months the result pushed browsers, certificate authorities and version-control systems to drop SHA-1 for anything security-sensitive. Git added collision detection. TLS certificates signed with SHA-1 were phased out. The lesson reached far past one algorithm: a function can look safe for years and still fall the moment the maths and the hardware line up.

The research and the people behind it

SHAttered was the work of Marc Stevens and Pierre Karpman at CWI Amsterdam, together with Elie Bursztein, Ange Albertini and Yarik Markov at Google. It built on years of earlier cryptanalysis of the SHA-1 design. The full technical paper that documents the method is preserved here.

Beyond the collision

The same questions that drove SHAttered run through everything we cover here: how hashing works, where it is used, and how systems prove they have not cheated. These guides pick up where the research leaves off.

What you'll find on shattered.io today