Clustered 2 filings across 2 jurisdictions · filing window Jul 11, 2025 → Aug 22, 2025. View entity profile → Other incidents for this victim →
incident inc_03e373c4bb9f4371 · merge_method deterministic · confidence 95%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · 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.
CA VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 27, 2025 → Feb 6, 2025
When the intrusion reportedly occurred, per the linked filings
Feb 6, 2025
Reported by VERMONT AG, CALIFORNIA AG filings
Episource, LLC notified consumers of a data breach occurring between Jan 27 and Feb 6, 2025. Criminals accessed and copied data including contact info, health insurance data, health data, and SSNs/DOB. Episource engaged law enforcement, turned off systems, and offers 2 years of credit monitoring. No misuse of data known to date.
Episource, LLC reported a data breach affecting patient and member data. Unauthorized access occurred between January 27, 2025, and February 6, 2025, when a criminal viewed and copied data including health insurance details, medical records, and personal information such as names, addresses, and Social Security numbers. The incident was discovered on February 6, 2025. Episource engaged forensic investigators, notified law enforcement, and shut down systems to contain the breach. Affected individuals are offered two years of credit monitoring.
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.