Clustered 2 filings across 2 jurisdictions · filed Mar 3, 2025. View entity profile → Other incidents for this victim →
incident inc_e1a5b19d60f74b84 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Health (basic)
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.
MD VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 19, 2024 → May 29, 2024
When the intrusion reportedly occurred, per the linked filings
May 29, 2024
Reported by VERMONT AG, MARYLAND AG filings
The Longleaf Network, LLC notified consumers of a data breach where an unauthorized actor accessed its network between May 19 and May 29, 2024. The incident potentially exposed names and other personal information. Longleaf contained the incident, investigated, notified law enforcement, and offered credit monitoring services.
The Longleaf Network, LLC reported a cybersecurity incident to the Maryland Attorney General on March 3, 2025. Between May 19 and May 29, 2024, an unauthorized actor accessed the company's network, potentially exposing the name and health insurance information of one Maryland resident. The company contained the incident, investigated the scope, and provided one year of complimentary credit monitoring through Experian to the affected individual. No evidence of misuse was found.
Affected (this filing): 1
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.