Breach Retrospectives

The Yahoo Mega-Breach: Password Security and the Cost of Delay

TechnicalGrey Cybersecurity team2 min readYahoo
Management

For leadership: the 60-second summary

In short
A series of intrusions at Yahoo, starting in 2013, eventually affected about three billion accounts — and weren't fully disclosed for years.
Why it matters
Weak password protection and slow disclosure multiplied the damage. Verizon cut its purchase price for Yahoo by US$350 million after the breaches came to light.
Questions to ask your team
  • How are customer passwords protected in our systems?
  • How quickly would we detect a breach?
  • Do we have a plan for timely, honest disclosure?

The full technical detail follows.More plain-English guides

The Yahoo breach, disclosed in September 2016, remains one of the largest data compromises in history, affecting over three billion accounts. The incident was not a single event but a series of intrusions dating back to 2013. It exposed fundamental failures in password storage, detection, and timely disclosure.

1. The Attack Vector and Scope

Attackers leveraged forged cookies—signed session tokens that allowed access to accounts without a password—alongside stolen credentials. The cookie-forgery technique highlighted how trust in authentication artifacts can be exploited when the underlying signing keys are compromised. The true scope, later revised to 3 billion accounts, was vastly underestimated during initial disclosure.

2. Password Storage Failures

The compromised credential database used legacy hashing, specifically MD5, often unsalted. MD5 is cryptographically broken and trivially brute-forced at scale. The absence of per-user salts allowed massively parallel offline cracking. This case became the canonical example of why modern password storage mandates adaptive, salted one-way functions such as bcrypt or Argon2.

3. Detection and Response Gaps

The intrusion persisted for years without detection, reflecting weak network monitoring and log analysis. Attackers established long-term persistence and were able to move laterally and access the credential store. The delayed disclosure—years after the initial compromise—compounded the risk to users and damaged trust.

4. Prevention and Modern Controls

Preventing a similar breach requires strong password hashing with per-user salts, robust session management with key rotation, comprehensive telemetry and anomaly detection, and rapid incident disclosure. Enabling multi-factor authentication and enforcing credential rotation for affected users are essential post-breach controls.

The Yahoo breach is a stark lesson in the cost of inadequate password security and delayed response. Modern defense must prioritize cryptographic strength, detection capability, and the discipline of timely transparency.

Want to know where you stand?

Our specialists can assess your exposure and help you prioritize what to fix first.

Book a consultation