Clustered 4 filings across 4 jurisdictions · filed May 8, 2024. View entity profile → Other incidents for this victim →
incident inc_d514fcae13434491 · 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 MT NH TX
HHS OCR · State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Mar 6, 2023
When the intrusion reportedly occurred, per the linked filings
Dec 28, 2023
Reported by NEW HAMPSHIRE AG filing
WebTPA Employer Services, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-05-08. The breach occurred from 3/6/2023 to 5/12/2023. 4,423 Montana residents were affected.
Affected (this filing): 4,423
WebTPA Employer Services, LLC reported to HHS on 2024-05-08 a Hacking/IT Incident affecting 2518533 individuals. Breached information located on Network Server. Business Associate present.
Affected (this filing): 2,518,533
WebTPA Employer Services, LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2023-03-06 and was reported on 2024-05-08. 20,085 Indiana residents were affected. 2,429,175 individuals affected in total.
Affected (this filing): 2,429,175
WebTPA Employer Services, LLC reported a data security incident to the New Hampshire Attorney General on May 8, 2024. Unauthorized access occurred via a VPN connection starting March 6, 2023, with exfiltration between April 18-23, 2023. The breach affected at least 3,510 New Hampshire residents, exposing eligibility files containing personal information. WebTPA notified law enforcement, engaged third-party experts, and offered complimentary identity monitoring services to affected individuals.
Affected (this filing): 3,510
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.