All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed3 filings · 2 statesUnverified claimConfirmedEnforcedpayoutskinghigh sensitivity

Merged incident · 3 filings

SunSource — March 2026 breach

Clustered 3 filings across 3 jurisdictions · filing window Apr 20, 2026 → Jun 17, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

First → last filing

Apr 20, 2026 → Jun 17, 2026

Merge confidence

100%

incident inc_91c186874c1c4d65 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Mar 31, 2026–Apr 5, 2026. 31 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Leak precedence

57days 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

58days

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

No cross-filing comparison data available for this incident.

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.