MORGAN STANLEY — January 2016 breach
Clustered 7 filings across 6 jurisdictions · filed Jul 10, 2020. View entity profile → Other incidents for this victim →
incident inc_f8d5e1a74aed4e63 · merged by deterministic · confidence 100%
Litigation Timing
Time between earliest and latest filing
Not recorded for this incident
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.
Sensitive data
identity_governmentIncident timeline
No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.
Member cascade — every filing about this breach
- JUL 10OR AGOR AG noticefirst filing · states nationwide total 209,881day 0
- JUL 10WA AGWA AG notice401,246 WA residentsoperator-confirmedday 0
- JUL 10MT AGMT AG notice32,370 MT residentsoperator-confirmedday 0
- JUL 10CA AGCA AG noticeno count statedauto-linkedday 0
- JUL 10NH AGNH AG notice77,296 NH residentsauto-linkedday 0
- JUL 10MA AGMA AG notice1,799 MA residentsauto-linkedday 0
- JUL 10MA AGMA AG noticemost recent · 389,969 MA residentsauto-linkedday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Jan 1, 2016 – Dec 31, 2019 CA AG
- Discovered
- —
- Data types
- Financial account · Identity (basic) · Government ID WA AG + MT AG + CA AG +2
- Attack vector
- Third-Party / Supply Chain WA AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Affected residents by state
per-state reported counts
State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
0 days
Cadence
~1 / 0d
vs. multi-state median
20.0× faster
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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.