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

Anchorage Neighborhood Health Center — August 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window Nov 19, 2025 → Nov 26, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

70,555

First → last filing

Nov 19, 2025 → Nov 26, 2025

Merge confidence

100%

incident inc_5b091f6c6c174484 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Aug 24, 2025–Aug 25, 2025, discovered Oct 10, 2025 — the first regulatory filing landed 40 days later. 70,555 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 7-day schedule across 11 filings beginning Nov 19, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
40days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
7days

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 clocksMaine⏱ ME AG >30d · 40dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 24, 2025breach begins
Oct 10, 2025discovered
notification delay · 40 days
Nov 19, 2025first filing
Nov 26, 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 19IN AGIN AG noticefirst filing · states nationwide total 70,555day 0
  2. NOV 19MT AGMT AG notice331 MT residentsday 0
  3. NOV 19NE AGNE AG noticeno count statedday 0
  4. NOV 19ME AGME AG notice54 ME residentsday 0
  5. NOV 19HHS OCRHHS OCR noticestates nationwide total 70,555day 0
  6. NOV 19CA AGCA AG noticeno count statedday 0
  7. NOV 19OR AGOR AG noticestates nationwide total 70,555day 0
  8. NOV 21TX AGTX AG noticestates nationwide total 70,555+2d
  9. NOV 24NH AGNH AG notice36 NH residents+5d
  10. NOV 25MA AGMA AG notice106 MA residents+6d
  11. NOV 26WA AGWA AG noticemost recent · 3,226 WA residents+7d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 24, 2025
IN AG
Discovered
Oct 10, 2025· 47d undetected
NE AG + ME AG + OR AG +3
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + NE AG + ME AG +6
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)

70,555

Sum of filed state slices

6,177· 8.8% of stated

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

US70,555
WA3,226
TX2,191
MT331
IN233
MA106
ME54
NH36

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

7 days

Cadence

~1 / 0.7d

vs. multi-state median

1.1× faster

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.