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

Sunflower Medical Group — December 2024 breach

Clustered 12 filings across 10 jurisdictions · filing window Dec 15, 2024 → May 12, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

220,968

First → last filing

Dec 15, 2024 → May 12, 2025

Merge confidence

100%

incident inc_4382ef6bac414520 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Dec 15, 2024, discovered Jan 7, 2025 — the first regulatory filing landed 53 days later (flagged late). 220,968 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 2 more. Notifications rolled out on a 148-day schedule across 10 filings beginning Dec 15, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
53days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
76days 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
148days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 59dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 15, 2024breach begins
Jan 7, 2025discovered
notification delay · 53 days
Mar 1, 2025first filing
May 12, 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. DEC 15Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. JAN 7Leak siterhysida postattacker claim · unverified+23d
  3. MAR 1IL AGIL AG noticeno count stated+76d
  4. MAR 7ME AGME AG noticestates nationwide total 220,968+82d
  5. MAR 7MA AGMA AG notice56 MA residents+82d
  6. MAR 7CA AGCA AG noticeno count stated+82d
  7. MAR 7NE AGNE AG noticeno count stated+82d
  8. MAR 7HHS OCRHHS OCR noticestates nationwide total 220,968+82d
  9. MAR 7MT AGMT AG notice41 MT residents+82d
  10. MAR 7VT AGVT AG noticeno count stated+82d
  11. MAR 10NH AGNH AG notice19 NH residents+85d
  12. MAY 12VT AGVT AG noticemost recent · no count stated+148d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 15, 2024
ME AG
Discovered
Jan 7, 2025· 23d undetected
IL AG + ME AG + CA AG +4
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + MA AG + CA AG +6
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)

220,968

Sum of filed state slices

152· 0.1% of stated

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

US220,968
MA56
MT41
ME36
NH19

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 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

148 days

Cadence

~1 / 13.5d

vs. multi-state median

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