DisclosureLens
HHS OCRState AGConfirmed5 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 5 filings

Little Hill Foundation for the Rehabilitation of Alcoholics, Inc. — May 2020 breach

Clustered 5 filings across 4 jurisdictions · filing window Jun 16, 2021 Jun 21, 2021. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

2,565

First → last filing

Jun 16, 2021 Jun 21, 2021

Merge confidence

100%

incident inc_5da8d6d5b8d04e2a · merged by llm · confidence 100%

Part of the BLACKBAUD, INC. supply-chain incident (2020)at least 175 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 5 regulatory filings. Intrusion May 1, 2020–Jul 16, 2020, discovered Oct 15, 2020 — the first regulatory filing landed 244 days later (flagged late). 2,565 individuals reported across the linked filings. Data reported: Health (basic), Identity (basic), and Financial account. Notifications rolled out on a 5-day schedule across 5 filings beginning Jun 16, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
244days

Discovered → first regulatory filing

Discovery variance
186days

Range of discovered_at dates across filings

Filing span
5days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >90d · 244dHIPAA HHS notifiedFull clock table in Litigation Timeline

Incident timeline

May 1, 2020breach begins
Oct 15, 2020discovered · members disagree
notification delay · 244 days
Jun 16, 2021first filing
Jun 21, 2021most 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. JUN 16ME AGME AG noticefirst filing · states nationwide total 2,565day 0
  2. JUN 16HHS OCRHHS OCR noticestates nationwide total 2,565day 0
  3. JUN 16IN AGIN AG noticestates nationwide total 2,565day 0
  4. JUN 16ME AGME AG noticestates nationwide total 2,565day 0
  5. JUN 21NH AGNH AG noticemost recent · 9 NH residents+5d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 1, 2020
ME AG
Discovered
Oct 15, 2020ME AG + NH AGApr 19, 2021ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic)
HHS OCR + NH AG
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)

2,565

Sum of filed state slices

30· 1.2% of stated

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

US2,565
IN14
NH9
ME7

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 filing5 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
llm
Confidence
1.00 · above the 0.85 auto-merge floor
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

5 days

Cadence

~1 / 1.3d

vs. multi-state median

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