DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed5 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedabysshigh sensitivity
Merged incident · 5 filings

HIGH POINT TREATMENT CENTER, INC. — June 2025 breach

Clustered 5 filings across 4 jurisdictions · filing window Jul 26, 2025 → Jan 30, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

3

Affected · reported

25,832

First → last filing

Jul 26, 2025 → Jan 30, 2026

Merge confidence

100%

incident inc_d98fd25682f34e6d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jun 17, 2025–Jul 6, 2025, discovered Jul 6, 2025 — the first regulatory filing landed 23 days later (flagged late). 25,832 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Employment, and 2 more. Notifications rolled out on a 187-day schedule across 4 filings beginning Jul 26, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
23days

Discovered → first regulatory filing

Discovery variance
10days

Range of discovered_at dates across filings

Leak precedence
2days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
187days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 13dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 17, 2025breach begins
Jul 6, 2025discovered · members disagree
notification delay · 23 days
Jul 29, 2025first filing
Jan 30, 2026most 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 26Leak siteabyss postfirst filing · attacker claim · unverifiedday 0
  2. JUL 29MA AGMA AG notice25,395 MA residents+3d
  3. JUL 29ME AGME AG noticestates nationwide total 4,613+3d
  4. AUG 5NH AGNH AG notice15 NH residents+10d
  5. JAN 30HHS OCRHHS OCR noticemost recent · states nationwide total 25,832+188d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 17, 2025 – Jul 6, 2025
ME AG
Discovered
Jul 6, 2025NH AGJul 16, 2025ME AGfilings disagree on discovery
Data types
Employment · Health (basic) · Identity (basic) · Government ID · PHI
MA AG + ME AG + NH AG +1
Attack vector
Unauthorized Access
ME 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)

25,832

Sum of filed state slices

25,414· 98.4% of stated

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

US25,832
MA25,395
NH15
ME4

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing4 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 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

187 days

Cadence

~1 / 46.8d

vs. multi-state median

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