DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed11 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

The Phia Group, LLC — July 2024 breach

Clustered 11 filings across 8 jurisdictions · filing window Jan 30, 2026 → May 22, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

1,512,742

First → last dated filing

Jan 30, 2026 → May 22, 2026

Merge confidence

100%

incident inc_1a6110e8e72d4592 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Jul 8, 2024–Jul 9, 2024, discovered Jul 9, 2024. 1,512,742 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 4 more. Notifications rolled out on a 112-day schedule across 8 dated filings beginning Jan 30, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
510days

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 >90dOregon✗ OR AG >45dTexas✗ TX AG >30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Jul 8, 2024breach begins
Jul 9, 2024discovered · members disagree
Jan 30, 2026first dated filing
May 22, 2026most 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. JAN 28NE AGNE AG noticefiling day not on record · 136 NE residents—
  2. JAN 30CA AGCA AG noticefirst filing · no count statedday 0
  3. JAN 30NH AGNH AG notice13 NH residentsday 0
  4. JAN 30WA AGWA AG notice28,692 WA residentsday 0
  5. FEB 1IL AGIL AG noticefiling day not on record · no count stated—
  6. FEB 7OR AGOR AG noticestates nationwide total 40,366+8d
  7. APR 23NE AGNE AG noticefiling day not on record · no count stated—
  8. MAY 14NH AGNH AG notice1,433 NH residents+104d
  9. MAY 15CA AGCA AG noticeno count stated+105d
  10. MAY 20SC AGSC AG noticestates nationwide total 3,470+110d
  11. MAY 22TX AGTX AG noticemost recent · states nationwide total 1,512,742+112d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 8, 2024 – Jul 9, 2024
NE AG
Discovered
Jul 9, 2024NE AG + CA AG + NH AG +3Dec 1, 2025OR AG + TX AGfilings disagree on discovery
Data types
Authentication · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NE AG + NH AG + WA AG +4
Attack vector
Unauthorized Access
NE 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)

1,512,742

Sum of filed state slices

154,672· 10.2% of stated

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

US1,512,742
TX121,354
WA28,692
SC3,057
NH1,433
NE136

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 filing11 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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 / 16d

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.