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

Heartland Alliance — January 2022 breach

Clustered 8 filings across 7 jurisdictions · filing window Feb 8, 2022 → Jan 1, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

54,914

First → last filing

Feb 8, 2022 → Jan 1, 2023

Merge confidence

100%

incident inc_e03d76e17a4949c5 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 1, 2022–Jan 31, 2022, discovered Jan 1, 2022 — the first regulatory filing landed 311 days later (flagged late). 54,914 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 4 more. Notifications rolled out on a 327-day schedule across 7 filings beginning Feb 8, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
311days

Discovered → first regulatory filing

Discovery variance
341days

Range of discovered_at dates across filings

Leak precedence
273days 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
327days

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 >180dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Jan 1, 2022breach begins
Jan 1, 2022discovered · members disagree
notification delay · 311 days
Nov 8, 2022first filing
Jan 1, 2023most 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. FEB 8Leak sitesuncrypt postfirst filing · attacker claim · unverifiedday 0
  2. NOV 8HHS OCRHHS OCR noticestates nationwide total 46,694+273d
  3. DEC 15IN AGIN AG noticestates nationwide total 54,914+310d
  4. DEC 15MT AGMT AG notice3 MT residents+310d
  5. DEC 19ME AGME AG noticestates nationwide total 54,914+314d
  6. DEC 20NH AGNH AG notice2 NH residents+315d
  7. DEC 20MA AGMA AG notice30 MA residents+315d
  8. JAN 1IL AGIL AG noticemost recent · no count stated+327d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 2, 2022
IN AG
Discovered
Jan 1, 2022MT AG + IL AGJan 31, 2022NH AGDec 8, 2022ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MT AG + NH AG +2
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)

54,914

Sum of filed state slices

272· 0.5% of stated

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

US54,914
IN234
MA30
MT3
ME3
NH2

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

327 days

Cadence

~1 / 46.7d

vs. multi-state median

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