WellLife Network Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-08-26 and was reported on 2024-08-29. 1 Indiana residents were affected. 52,150 individuals affected in total.
Affected (this filing): 52,150
Clustered 2 filings across 2 jurisdictions · filed Aug 29, 2024. View entity profile → Other incidents for this victim →
incident inc_1584f11aed3148f8 · 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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 26, 2023
When the intrusion reportedly occurred, per the linked filings
Sep 7, 2023
Reported by NEW HAMPSHIRE AG filing
WellLife Network Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-08-26 and was reported on 2024-08-29. 1 Indiana residents were affected. 52,150 individuals affected in total.
Affected (this filing): 52,150
WellLife Network Inc. reported an unauthorized access event affecting one New Hampshire resident. Suspicious activity was detected on September 7, 2023, covering an intrusion window of August 26–September 7, 2023. The incident involved potential access to personal information. WellLife engaged third-party cybersecurity specialists, notified federal law enforcement, and provided credit monitoring services. Notices were mailed on August 29, 2024.
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.