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

Northwestern Community Services Board — July 2024 breach

Clustered 5 records across 4 jurisdictions: 4 filings and 1 leak-site claim · filing window May 29, 2025 → Jul 8, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

4

Affected · reported

21,856

First → last dated filing

May 29, 2025 → Jul 8, 2025

Merge confidence

100%

incident inc_aa4ab1112dbd4a15 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 18, 2024, discovered May 12, 2025 — the first regulatory filing landed 17 days later. 21,856 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 1 more. Notifications rolled out on a 40-day schedule across 3 dated filings beginning May 29, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
17days

Discovered → first regulatory filing

Leak precedence
278days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
40days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 18, 2024breach begins
May 12, 2025discovered
notification delay · 17 days
May 29, 2025first dated filing
Jul 8, 2025most 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 and leak-site claim in this incident

  1. AUG 8Leak siteblacksuit postfirst record · attacker claim · unverifiedday 0
  2. MAY 29HHS OCRHHS OCR noticestates nationwide total 21,856+294d
  3. JUL 7NE AGNE AG noticefiling day not on record · no count stated—
  4. JUL 7ME AGME AG noticestates nationwide total 15,663+333d
  5. JUL 8MA AGMA AG noticemost recent · 6 MA residents+334d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 18, 2024
ME AG
Discovered
May 12, 2025· 298d undetected
ME AG
Data types
Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + MA AG + NE AG +1
Attack vector
Unauthorized Access
HHS OCR

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)

21,856

Sum of filed state slices

13· 0.1% of stated

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

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

40 days

Cadence

~1 / 20d

vs. multi-state median

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