Clustered 2 filings across 2 jurisdictions · filed Apr 12, 2021. View entity profile → Other incidents for this victim →
incident inc_d565457e94c14c61 · merge_method llm · confidence 44%
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.
Identity (basic) · Financial account · Financial credentials
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 21, 2020
When the intrusion reportedly occurred, per the linked filings
Apr 6, 2021
Reported by MAINE AG filing
Yeshiva University reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-12. The breach occurred from 12/21/2020 to 12/23/2020. 3 Montana residents were affected.
Affected (this filing): 3
Yeshiva University, an educational institution, experienced an external system breach (hacking) that occurred from December 21, 2020, to December 23, 2020. The breach was discovered on April 6, 2021. The compromised information included names or other personal identifiers in combination with financial account numbers or credit/debit card numbers and their associated security codes, access codes, passwords, or PINs. A total of 3,380 individuals were affected, including 7 residents of Maine. Affected individuals were notified on April 12, 2021, and offered one year of credit monitoring and identity theft protection services through Experian.
Affected (this filing): 7
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.