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

PH TECH, LLC — May 2023 breach

Clustered 8 filings across 7 jurisdictions · filing window Jul 10, 2023 → Aug 16, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

1,752,083

First → last filing

Jul 10, 2023 → Aug 16, 2023

Merge confidence

100%

incident inc_8eff4e1dd0da44ae · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion May 30, 2023, discovered Jun 2, 2023 — the first regulatory filing landed 38 days later. 1,752,083 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 37-day schedule across 8 filings beginning Jul 10, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
38days

Discovered → first regulatory filing

Discovery variance
14days

Range of discovered_at dates across filings

Filing span
37days

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 >30dMaine⏱ ME AG >30d · 56dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueCalifornia✓ CA 60-day OK · 60dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 30, 2023breach begins
Jun 2, 2023discovered · members disagree
notification delay · 38 days
Jul 10, 2023first filing
Aug 16, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 10WA AGWA AG noticefirst filing · 3,288 WA residentsday 0
  2. JUL 24OR AGOR AG noticestates nationwide total 1,700,000+14d
  3. JUL 31OR AGOR AG noticestates nationwide total 1,752,083+21d
  4. AUG 2MT AGMT AG notice199 MT residents+23d
  5. AUG 2MA AGMA AG notice63 MA residents+23d
  6. AUG 11ME AGME AG noticestates nationwide total 1,700,000+32d
  7. AUG 11NH AGNH AG noticeno count stated+32d
  8. AUG 16CA AGCA AG noticemost recent · no count stated+37d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023
WA AG
Discovered
Jun 2, 2023WA AG + MT AG + NH AGJun 16, 2023OR AG + ME AG + CA AGfilings disagree on discovery
Data types
Financial · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + MT AG + ME AG +3
Attack vector
Third-Party / Supply Chain· CLOP Group
WA 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,752,083

Sum of filed state slices

3,577· 0.2% of stated

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

US1,752,083
WA3,288
MT199
MA63
ME27

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 filing8 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 Jun 12, 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

37 days

Cadence

~1 / 5.3d

vs. multi-state median

4.6× 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.