/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

How the full dump of LinkedIn passwords from 2012 hack will speed cracking of hashed passwords from any future breaches

Jeremi M. Gosney / Ars Technica :

Ars Technica Jeremi M. Gosney

Context & Ripple Effects

The story sits at the end of a rapid sequence: the [[a:869828|117M LinkedIn email-and-password database from the 2012 hack surfaced for sale on a dark web marketplace]] in mid-May, followed days later by the same hacker claiming to hold 360M Myspace user emails with passwords. Jeremi M. Gosney's piece is the technical post-mortem on why that sale matters beyond LinkedIn itself.

First-order effects

  • Crackers now hold the full set of real-world LinkedIn passwords as a training corpus, letting them build dictionaries and rule sets tuned to how actual users chose passwords in that era.
  • Any LinkedIn user whose password from 2012 was reused elsewhere is immediately exposed, since the plaintext-equivalent material is now public rather than gated behind a paid marketplace listing.

Second-order effects

  • The same dynamic raises the value of adjacent old-breach dumps: the claimed Myspace trove and the Last.fm 2012 hack, where 96% of hashed passwords were cracked within two hours, become easier to finish because cross-site password reuse means each cracked corpus feeds the next.
  • Services with large legacy user bases face forced credential resets and stronger login checks, since attackers can automate reuse of the newly public LinkedIn passwords against them.

Third-order effects

  • Breaches stop being point-in-time events: a weakly hashed dump keeps paying out for years, so the cost of an old breach compounds as it becomes raw material for cracking every future one.
  • If the pattern holds, the burden shifts toward slower, salted-per-user hashing and faster forced rotation as the baseline defense, because the attacker side now industrializes every leak into permanent infrastructure.

The trend: Old breach dumps are compounding into permanent cracking infrastructure, so the damage of a poorly hashed leak grows with every subsequent breach rather than fading.