DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed21 filings · 14 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 21 filings

NAHGA Claim Services — April 2025 breach

Clustered 21 filings across 14 jurisdictions · filing window Nov 3, 2025 → Dec 16, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

21 filings

States

14

Affected · reported

181,160

First → last filing

Nov 3, 2025 → Dec 16, 2025

Merge confidence

100%

incident inc_e6e4accd104b4637 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 21 regulatory filings. Intrusion Apr 8, 2025–Apr 11, 2025, discovered Apr 10, 2025 — the first regulatory filing landed 207 days later (flagged late). 181,160 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 5 more. Notifications rolled out on a 43-day schedule across 21 filings beginning Nov 3, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
207days

Discovered → first regulatory filing

Discovery variance
236days

Range of discovered_at dates across filings

Filing span
43days

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 clocksVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 221dCalifornia✗ CA 60-day late · 239dOregon✗ OR AG >45dWashington✗ WA AG >90dHIPAA✓ HHS notifiedIowa✓ IA AG ≤5 bdaySouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Apr 8, 2025breach begins
Apr 10, 2025discovered · members disagree
notification delay · 207 days
Nov 3, 2025first filing
Dec 16, 2025most 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. NOV 3SC AGSC AG noticefirst filing · 430 SC residentsday 0
  2. NOV 14NE AGNE AG notice66 NE residents+11d
  3. NOV 14IN AGIN AG noticestates nationwide total 181,160+11d
  4. NOV 17VT AGVT AG noticeno count stated+14d
  5. NOV 17NH AGNH AG notice26 NH residents+14d
  6. NOV 17ME AGME AG noticestates nationwide total 5,072+14d
  7. NOV 17MT AGMT AG notice10 MT residents+14d
  8. NOV 19HHS OCRHHS OCR noticestates nationwide total 21,834+16d
  9. NOV 19TX AGTX AG noticestates nationwide total 5,072+16d
  10. DEC 1IL AGIL AG noticeno count stated+28d
  11. DEC 5NE AGNE AG notice773 NE residents+32d
  12. DEC 11IA AGIA AG notice929 IA residents+38d
  13. DEC 12SC AGSC AG notice4,381 SC residents+39d
  14. DEC 12ME AGME AG noticestates nationwide total 181,160+39d
  15. DEC 12NH AGNH AG notice337 NH residents+39d
  16. DEC 15MA AGMA AG notice1,017 MA residents+42d
  17. DEC 15CA AGCA AG noticestates nationwide total 146+42d
  18. DEC 15VT AGVT AG noticeno count stated+42d
  19. DEC 15OR AGOR AG noticestates nationwide total 181,160+42d
  20. DEC 15WA AGWA AG notice1,621 WA residents+42d
  21. DEC 16TX AGTX AG noticemost recent · states nationwide total 181,160+43d
  22. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 8, 2025 – Apr 10, 2025
SC AG
Discovered
Apr 10, 2025NE AG + VT AG + NH AG +7Apr 13, 2025SC AGOct 17, 2025TX AGDec 2, 2025IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PCI · PHI · PII
SC AG + NE AG + VT AG +10
Attack vector
Unauthorized Access
SC 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)

181,160

Sum of filed state slices

59,813· 33.0% of stated

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

US181,160
TX46,372
SC4,381
IN3,899
WA1,621
MA1,017
IA929
NE773
ME474
NH337
MT10

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 filing21 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 23, 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

43 days

Cadence

~1 / 2.2d

vs. multi-state median

5.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.