Live
Breaking
15m ago Cloud Computing Kubecost Setup: 12 Steps to Cut Kubernetes Costs 30% [2026] 2h ago Esports Fortnite Rank Tracker Setup: 12 Steps, 40 Min [2026] 4h ago Cryptocurrency Verify Stablecoin Reserves: 10 Steps, 45 Min [2026] 7h ago Esports Fortnite vs Valorant Ranks: 38% Bronze, 25 Tiers [2026] 8h ago Cryptography zk-SNARKs vs zk-STARKs: 384 Bytes vs 68KB Proofs [2026] 12h ago Cloud Computing Cloud IAM Fails Hit 98%, LiteLLM Breach Hits 434K [2026] 16h ago Cryptocurrency Tether’s First Audit: KPMG Confirms $6.8B Surplus [2026] 1d ago Cloud Computing Cloudflare Workers vs AWS Lambda@Edge: 800ms vs 1ms [2026] 1d ago Esports Marvel Rivals Rank Tracker Setup: 12 Steps, 30 Min [2026] 1d ago Cryptocurrency Solo Bitcoin Mining Setup: 12 Steps, 45 Min [2026] 1d ago Esports Marvel Rivals vs Valorant Ranks: 23 Steps vs 25 [2026] 1d ago Cryptography ECC vs RSA: 25x Faster Signing, Smaller Keys [2026] 1d ago Cloud Computing AWS Bedrock Web Search Goes GA, Google Ships 200+ Models [2026] 1d ago Cryptocurrency Boltz Founders Quit 10 Days After AI Bridge Shutdown [2026] 15m ago Cloud Computing Kubecost Setup: 12 Steps to Cut Kubernetes Costs 30% [2026] 2h ago Esports Fortnite Rank Tracker Setup: 12 Steps, 40 Min [2026] 4h ago Cryptocurrency Verify Stablecoin Reserves: 10 Steps, 45 Min [2026] 7h ago Esports Fortnite vs Valorant Ranks: 38% Bronze, 25 Tiers [2026] 8h ago Cryptography zk-SNARKs vs zk-STARKs: 384 Bytes vs 68KB Proofs [2026] 12h ago Cloud Computing Cloud IAM Fails Hit 98%, LiteLLM Breach Hits 434K [2026] 16h ago Cryptocurrency Tether’s First Audit: KPMG Confirms $6.8B Surplus [2026] 1d ago Cloud Computing Cloudflare Workers vs AWS Lambda@Edge: 800ms vs 1ms [2026] 1d ago Esports Marvel Rivals Rank Tracker Setup: 12 Steps, 30 Min [2026] 1d ago Cryptocurrency Solo Bitcoin Mining Setup: 12 Steps, 45 Min [2026] 1d ago Esports Marvel Rivals vs Valorant Ranks: 23 Steps vs 25 [2026] 1d ago Cryptography ECC vs RSA: 25x Faster Signing, Smaller Keys [2026] 1d ago Cloud Computing AWS Bedrock Web Search Goes GA, Google Ships 200+ Models [2026] 1d ago Cryptocurrency Boltz Founders Quit 10 Days After AI Bridge Shutdown [2026]
NewsroomLive
Today7 new
Archive323 stories
Last filed15m ago
Languages10
UTC20:28:19
Top Story Cloud Computing

Kubecost Setup: 12 Steps to Cut Kubernetes Costs 30% [2026]

Kubernetes bills keep climbing even when traffic doesn't. Idle pods, over-provisioned nodes, and forgotten dev clusters quietly eat budgets, and most teams only find out when finance forwards an invoice with a red circle around it.…

15m ago  ·  Aug 23, 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