Clustered 2 filings across 2 jurisdictions · filed Dec 11, 2025. View entity profile → Other incidents for this victim →
incident inc_22bce0df2ebe4f1a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
IN WA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 20, 2025
When the intrusion reportedly occurred, per the linked filings
Jun 20, 2025
Reported by WASHINGTON AG filing
Morningside reported a data breach to the Indiana Attorney General. The breach occurred on 2025-06-20 and was reported on 2025-12-11. 1 Indiana residents were affected. 1,564 individuals affected in total.
Affected (this filing): 1,564
Morningside, a non-profit/charity sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-06-20 and filed notice on 2025-12-11. 1,534 Washington residents were affected. 174 days elapsed between awareness and notification. 150 days to contain the breach.
Affected (this filing): 1,534
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.