Live
Breaking
59m ago Hardware & Chips A20 Pro Geekbench 7 Score Hits 4,042, Nears M5 Max [2026] 1h ago Cryptocurrency Mine Bitcoin at Home: ASIC Setup in 10 Steps [2026] 2h ago AI & Machine Learning GLM-5.2 Beats GPT-5.5 62.1 to 58.6, Trails Claude [2026] 3h ago Provably Fair Honkai Star Rail Pity Odds: 0.6% Rate, $361 Cap [2026] 3h ago Cybersecurity VMware vCenter RCE Hits CVSS 9.8, Ransomware Live [2026] 4h ago Esports Fortnite vs Marvel Rivals Ranks: 22 vs 23 Tiers [2026] 4h ago Gaming 007 First Light Hits 3rd Switch 2 Delay: March 2027 [2026] 5h ago Hardware & Chips Ugreen LinkStation Pro Adds 80Gbps, 850W PSU [2026] 9h ago Cloud Computing JetBrains Cadence Breach: CVSS 9.8 Bug Open 16 Days [2026] 10h ago Hardware & Chips macOS 27 Golden Gate Arrives, Locks Out Every Intel Mac [2026] 11h ago AI & Machine Learning AI Slowdown Call Sinks Nvidia, Lifts CrowdStrike 13% [2026] 13h ago Cybersecurity Revolut Breach Exposes IDs, IBANs of 680 Customers [2026] 13h ago Cryptocurrency Base L2 Tops $14.4B TVL on Just $8,800 in ETH Fees [2026] 14h ago Gaming Game Pass, PS Plus Cancellations: 40% Blame Cost [2026] 59m ago Hardware & Chips A20 Pro Geekbench 7 Score Hits 4,042, Nears M5 Max [2026] 1h ago Cryptocurrency Mine Bitcoin at Home: ASIC Setup in 10 Steps [2026] 2h ago AI & Machine Learning GLM-5.2 Beats GPT-5.5 62.1 to 58.6, Trails Claude [2026] 3h ago Provably Fair Honkai Star Rail Pity Odds: 0.6% Rate, $361 Cap [2026] 3h ago Cybersecurity VMware vCenter RCE Hits CVSS 9.8, Ransomware Live [2026] 4h ago Esports Fortnite vs Marvel Rivals Ranks: 22 vs 23 Tiers [2026] 4h ago Gaming 007 First Light Hits 3rd Switch 2 Delay: March 2027 [2026] 5h ago Hardware & Chips Ugreen LinkStation Pro Adds 80Gbps, 850W PSU [2026] 9h ago Cloud Computing JetBrains Cadence Breach: CVSS 9.8 Bug Open 16 Days [2026] 10h ago Hardware & Chips macOS 27 Golden Gate Arrives, Locks Out Every Intel Mac [2026] 11h ago AI & Machine Learning AI Slowdown Call Sinks Nvidia, Lifts CrowdStrike 13% [2026] 13h ago Cybersecurity Revolut Breach Exposes IDs, IBANs of 680 Customers [2026] 13h ago Cryptocurrency Base L2 Tops $14.4B TVL on Just $8,800 in ETH Fees [2026] 14h ago Gaming Game Pass, PS Plus Cancellations: 40% Blame Cost [2026]
NewsroomLive
Today21 new
Archive758 stories
Last filed59m ago
Languages10
UTC17:25:18
Top Story Hardware & Chips

A20 Pro Geekbench 7 Score Hits 4,042, Nears M5 Max [2026]

A leaked Geekbench 7 result for Apple's next mobile processor is making the rounds this week, and the number attached to it is why engineers and chip analysts are paying attention. According to a report from…

59m ago  ·  Sep 15, 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