Clustered 2 filings across 2 jurisdictions · filing window May 8, 2024 → Jul 22, 2024. View entity profile → Other incidents for this victim →
incident inc_152284a3ec214ed1 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
SC WA
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.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 18, 2023 → Apr 23, 2023
When the intrusion reportedly occurred, per the linked filings
Dec 28, 2023
Reported by WASHINGTON AG, SOUTH CAROLINA AG filings
WebTPA, a business sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2023-12-28 and filed notice on 2024-05-08. 38,420 Washington residents were affected. 132 days elapsed between awareness and notification. 297 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 38,420
WebTPA Employer Services, LLC reported a data breach to the South Carolina Department of Consumer Affairs on July 22, 2024, covering a notification sent on May 8, 2024. The incident involved unauthorized access to systems between April 18 and 23, 2023, affecting approximately 2.5 million individuals. The breach compromised protected health information (PHI), Social Security numbers, driver's license numbers, and financial account data. WebTPA, a healthcare administrator, secured its network and engaged third-party forensic experts.
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.
Affected (this filing): 2,500,000