Confirmed breach. Intrusion Jun 8, 2019–Jun 23, 2019, discovered Jun 22, 2019 — the first regulatory filing landed 11 days later. 1 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksCalifornia✓ CA 60-day OK · 3dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
1
Data types
—
Jurisdictions
2
CA MT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 8, 2019 → Jun 23, 2019
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Jun 22, 2019
Reported by CALIFORNIA AG filing
🐻California State AGFirst filinglinked via multistate filing link · 95%
Sprint reported unauthorized access to customer accounts via the Samsung.com 'add a line' website. Attackers used valid account credentials to view personal information including names, addresses, phone numbers, and billing details. Sprint secured accounts and reset PINs. No financial data beyond billing addresses was compromised.
Sprint reported a data breach to the Montana Attorney General. The breach was reported on 2019-07-11. The breach occurred from 6/22/2019 to 6/25/2019. 1 Montana residents were affected.
Affected (this filing): 1
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.