Clustered 2 filings across 2 jurisdictions · filed Mar 14, 2022. View entity profile → Other incidents for this victim →
incident inc_092d16a3fbd045c1 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Financial account · Financial credentials
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
DE ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 17, 2022
When the intrusion reportedly occurred, per the linked filings
Jan 27, 2022
Reported by DELAWARE AG filing
Feb 7, 2022
Reported by MAINE AG filing
Winterthur Museum, Garden & Library experienced an external system breach on January 17, 2022, which was discovered on February 7, 2022. The breach affected 4 Maine residents, compromising their names and financial account or card numbers. In response, the entity offered 12 months of credit monitoring and identity restoration services through Experian.
Affected (this filing): 4
Winterthur Museum, Garden & Library notified Delaware AG of a data event discovered Jan 27, 2022, involving unauthorized access to computer systems starting Jan 17, 2022. An unknown actor accessed files containing names. No evidence of misuse was found. The museum engaged forensic specialists, secured systems, and offered complimentary credit/identity monitoring via Experian. The notice covers residents of multiple states including DE, DC, MD, NY, NC, RI, and NM.
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.