Clustered 3 filings across 3 jurisdictions · filing window Jan 29, 2025 → Mar 28, 2025. View entity profile → Other incidents for this victim →
incident inc_407daf9d7cd449ae · 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.
Government ID · Identity (basic)
CA IN MD
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 14, 2024
When the intrusion reportedly occurred, per the linked filings
Mar 15, 2024
Reported by MARYLAND AG filing
Lyon Management Group Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-03-14 and was reported on 2025-01-29. 1 Indiana residents were affected. 195 individuals affected in total.
Affected (this filing): 195
Lyon Management Group, Inc. notified the Maryland Attorney General of a data event affecting 4 Maryland residents. An unknown actor accessed systems and potentially copied files containing names, driver's license numbers, and Social Security numbers between March 14-15, 2024. Lyon secured systems, notified federal law enforcement, and provided 12 months of credit monitoring via TransUnion.
Affected (this filing): 4
Lyon Management Group, Inc. experienced unauthorized access to its IT network between March 14–15, 2024, during which an unknown actor potentially copied files containing personal information. The company secured its systems, conducted a forensic investigation, notified federal law enforcement, and offered complimentary credit monitoring and identity restoration services through TransUnion. Notice letters were sent on or around March 28, 2025.
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.