DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
SEC 8-KConfirmed5 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Merged incident · 5 filings

River Financial Corporation — June 2026 breach

Clustered 5 filings across 1 jurisdiction · filing window Jun 25, 2026 → Jul 30, 2026. View entity profile → Other incidents for this victim →

✓ data types, discovery date agreeMerge100%

Determination

Confirmed

Members

5 filings

States

1

Affected · reported

—

First → last filing

Jun 25, 2026 → Jul 30, 2026

Merge confidence

100%

incident inc_4a3ee88d5fe54477 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. Intrusion Jun 16, 2026, discovered Jun 19, 2026 — the first regulatory filing landed 7 days later (flagged late). Data reported: PII. Notifications rolled out on a 34-day schedule across 5 filings beginning Jun 25, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
7days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Materiality delta
0days

Discovery to SEC materiality determination

SEC filing delay
6days

Materiality determination to SEC 8-K filing

Filing span
34days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksSEC✗ SEC 4-day late · 17dFull clock table in Litigation Timeline

Incident timeline

Jun 16, 2026breach begins
Jun 19, 2026discovered
notification delay · 7 days
Jun 25, 2026first filing
Jul 30, 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. JUN 25SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. JUL 6SEC 8-KSEC 8-K noticeno count stated+11d
  3. JUL 10SEC 8-KSEC 8-K noticeno count stated+15d
  4. JUL 17SEC 8-KSEC 8-K noticeno count stated+22d
  5. JUL 30SEC 8-KSEC 8-K noticemost recent · no count stated+35d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 16, 2026
SEC 8-K
Discovered
Jun 19, 2026· 3d undetected
SEC 8-K
Data types
PII
SEC 8-K
Attack vector
Ransomware
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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 filing

No regulator filing linked yet.

SEC 8-K / victim statement5 members

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-confirmed · 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

34 days

Cadence

~1 / 8.5d

vs. multi-state median

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