DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed13 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 13 filings

WebTPA Employer Services, LLC — March 2023 breach

Clustered 13 filings across 10 jurisdictions · filing window Apr 1, 2024 → Jul 22, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

10

Affected · reported

2,518,533

First → last dated filing

Apr 1, 2024 → Jul 22, 2024

Merge confidence

100%

incident inc_d514fcae13434491 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. The filings describe unauthorized access. Intrusion Mar 6, 2023–May 12, 2023, discovered Mar 6, 2023 — the first regulatory filing landed 392 days later; 3 later filings were flagged late. 2,518,533 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 112-day schedule across 12 dated filings beginning Apr 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
392days

Discovered → first regulatory filing

Discovery variance
297days

Range of discovered_at dates across filings

Filing span
112days

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.

Regulatory clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 132dHawaii✓ HI CRA notice dueHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 6, 2023breach begins
Mar 6, 2023discovered · members disagree
notification delay · 392 days
Apr 1, 2024first dated filing
Jul 22, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. APR 1HI AGHI AG noticefirst filing · 4,972 HI residentsday 0
  2. APR 23CA AGCA AG noticeno count stated+22d
  3. MAY 1IL AGIL AG noticefiling day not on record · no count stated—
  4. MAY 8IN AGIN AG noticestates nationwide total 2,429,175+37d
  5. MAY 8WA AGWA AG notice41,600 WA residents+37d
  6. MAY 8MT AGMT AG notice4,423 MT residents+37d
  7. MAY 8CA AGCA AG noticeno count stated+37d
  8. MAY 8HHS OCRHHS OCR noticestates nationwide total 2,518,533+37d
  9. MAY 8NH AGNH AG notice3,510 NH residents+37d
  10. MAY 10MA AGMA AG notice37,012 MA residents+39d
  11. JUL 19CA AGCA AG noticeno count stated+109d
  12. JUL 22NH AGNH AG notice5,778 NH residents+112d
  13. JUL 22SC AGSC AG noticemost recent · 62,138 SC residents+112d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 18, 2023 – Apr 23, 2023
HI AG
Discovered
Mar 6, 2023IL AG + WA AGDec 28, 2023HI AG + CA AG + MT AG +2filings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
HI AG + CA AG + WA AG +4
Attack vector
Unauthorized Access
HI AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

2,518,533

Sum of filed state slices

176,008· 7.0% of stated

93% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US2,518,533
SC62,138
WA41,600
MA37,012
IN20,085
NH5,778
HI4,972
MT4,423

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing13 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

112 days

Cadence

~1 / 10.2d

vs. multi-state median

18.7× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.