Clustered 2 filings across 1 jurisdiction · filing window Apr 23, 2021 → Aug 10, 2021. View entity profile → Other incidents for this victim →
incident inc_5af6fca274ab4049 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
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.
Financial account · Financial credentials
ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 15, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 24, 2021
Reported by MAINE AG filings
Lydall, Inc. experienced a ransomware attack on March 15, 2021, which was discovered on March 24, 2021. The breach affected 21 Maine residents, compromising their names and Social Security numbers. The company notified affected individuals on April 26, 2021, and offered one year of credit monitoring services through LifeLock.
Affected (this filing): 21
Lydall, Inc. reported a ransomware attack that occurred on March 15, 2021, and was discovered on March 24, 2021. The breach affected 21 Maine residents, and a total of 3100 individuals. The compromised information includes names or other personal identifiers in combination with financial account numbers or credit/debit card numbers with their security codes. Lydall offered one year of credit monitoring services through LifeLock to the affected individuals.
Affected (this filing):
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.