Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksCalifornia✓ CA 60-day OK · 8dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
—
Data types
2
Credentials · PII
Jurisdictions
1
CA
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 1, 2012 → Dec 31, 2012
When the intrusion reportedly occurred, per the linked filings
LinkedIn Corporation notified California AG that data from a 2012 breach (email addresses, hashed passwords, member IDs) was made available online in May 2016. LinkedIn invalidated passwords for affected legacy accounts, engaged law enforcement, and enhanced security (salted hashes, 2FA). No new hack occurred; this was a re-use of old credentials.
CA 60-day OK · 8d
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.