Clustered 3 filings across 3 jurisdictions · filing window Apr 5, 2023 → Jul 12, 2023. View entity profile → Other incidents for this victim →
incident inc_fe7fb7734bc5430a · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Identity (basic) · Government ID
ME VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 2, 2023
When the intrusion reportedly occurred, per the linked filings
Mar 6, 2023
Reported by MAINE AG, VERMONT AG filings
"UnitedLex delivers unparalleled transformation for legal and business in the Digital Age. We are committed to excellence in every aspect of our client, employee, and community relationships."
UnitedLex Corporation reported an external system breach that occurred on March 2, 2023, and was discovered on March 6, 2023. The breach affected 4 Maine residents, compromising their names and Social Security numbers. Affected individuals were notified on July 12, 2023, and offered 12 months of identity restoration services through Kroll.
UnitedLex Corporation notified consumers of a data security incident discovered on March 6, 2023, where an unauthorized actor accessed the corporate environment and took data. Impacted data likely included names, SSNs, payroll financial account numbers, and benefits information. UnitedLex engaged cybersecurity experts, reset passwords, and provided 24 months of credit monitoring and identity protection services via Kroll.
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.
Affected (this filing): 4