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

illumifin — October 2025 breach

Clustered 12 filings across 11 jurisdictions · filing window Mar 1, 2026 → Apr 22, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

11

Affected · reported

97,781

First → last filing

Mar 1, 2026 → Apr 22, 2026

Merge confidence

100%

incident inc_01f3e075ff6e4458 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Oct 28, 2025–Nov 4, 2025, discovered Nov 4, 2025 — the first regulatory filing landed 117 days later (flagged late). 97,781 individuals reported across the linked filings. Data reported: Government ID, Health (basic), PHI, and 3 more. Notifications rolled out on a 52-day schedule across 12 filings beginning Mar 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
117days

Discovered → first regulatory filing

Discovery variance
113days

Range of discovered_at dates across filings

Filing span
52days

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 clocksCalifornia✗ CA 60-day late · 113dOregon✗ OR AG >45dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 28, 2025breach begins
Nov 4, 2025discovered · members disagree
notification delay · 117 days
Mar 1, 2026first filing
Apr 22, 2026most 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. MAR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 10HHS OCRHHS OCR noticestates nationwide total 5,385+9d
  3. MAR 13NE AGNE AG notice3 NE residents+12d
  4. MAR 31IN AGIN AG noticestates nationwide total 43,152+30d
  5. MAR 31NH AGNH AG notice15 NH residents+30d
  6. MAR 31MA AGMA AG noticeno count stated+30d
  7. MAR 31MT AGMT AG notice795 MT residents+30d
  8. MAR 31CA AGCA AG noticeno count stated+30d
  9. APR 2TX AGTX AG noticestates nationwide total 41,948+32d
  10. APR 7SC AGSC AG notice2,507 SC residents+37d
  11. APR 22NH AGNH AG notice37 NH residents+52d
  12. APR 22OR AGOR AG noticemost recent · states nationwide total 97,781+52d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 4, 2025
IN AG
Discovered
Nov 4, 2025NE AG + NH AG + MT AG +3Feb 25, 2026IL AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + HHS OCR + NH AG +6
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)

97,781

Sum of filed state slices

13,173· 13.5% of stated

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

US97,781
TX6,724
IN3,107
SC2,507
MT795
NH37
NE3

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

52 days

Cadence

~1 / 4.7d

vs. multi-state median

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