Google Cloud has opened a new front in the fight for enterprise Kubernetes workloads. On September 25, 2026, the company's containers and Kubernetes team published a post titled "Introducing GKE agentic migration for AI-assisted EKS-to-GKE migrations…
The L.A. Noire 2 rumor mill is spinning again. Fifteen years after Rockstar Games and Team Bondi shipped…
Renting a Nvidia B200 by the hour now costs more per unit of AI compute than renting an…
Desktop graphics card shipments climbed to 12.5 million units in the second quarter of 2026, the highest quarterly total since the first…
A new login method can succeed or fail based on how it is introduced. Employees who understand a change tend to adopt…
A five-prompt test that Tom's Guide published on September 28, 2026 is doing something that dozens of benchmark leaderboards haven't managed all…
A Starknet lending protocol just handed the DeFi industry another lesson in why a "valid" price and a "usable" price are not…
Cold Iron Studios has confirmed staff layoffs while working on Aliens: Fireteam Elite 2, and the fallout has already reached the game's…
Beijing is taking a closer look at Broadcom's hardware inside Chinese state-backed data centers, according to a Financial Times report relayed by…
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.
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.
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.
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.
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.
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 pressure only grew from there. In January 2020, Gaëtan Leurent and Thomas Peyrin published SHA-1 is a Shambles, a chosen-prefix collision that could be rented for roughly $45,000, and on 15 December 2022 NIST formally retired SHA-1 altogether, giving everyone until the end of 2030 to phase it out for good.
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.
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.
Hash functions, the SHA family, encryption and digital signatures.
Breaches, passwords, TLS and staying secure online.
VPNs, Tor, encrypted messaging and staying anonymous.
How blockchains use hashing, wallets and crypto safety.
How SHA-256 lets you verify an outcome for yourself.
Beyond the original SHA-1 collision proof, the site now publishes ongoing coverage across cryptography, cybersecurity, privacy, cryptocurrency and provably-fair systems. Every article is editorial, lightly-opinionated and built on primary sources where possible.
Deep-dives into the maths that secures the internet: hash functions, digital signatures, the SHA family and the SHAttered collision that gave this site its name. Explainers and reporting for people who want to understand how the primitives actually work.
Breaches, CVE post-mortems, zero-day reporting and practical defense. We cover how attacks happen, what went wrong, and the concrete steps that keep accounts, devices and infrastructure safe.
VPNs, Tor, encrypted messaging and the surveillance landscape. Reporting and guides on protecting your data, understanding tracking, and taking back control of what you share online.
Blockchain hashing, wallets and on-chain incidents. Clear-eyed coverage of how crypto works under the hood, the security trade-offs, and the hacks and exploits worth learning from.