FEDERALItem 1.05 · mandatoryHackingFinancial ServicesFinanceData ExfiltratedDelayed DiscoveryPIILowActive

River Financial Corporation

bd_a605d6d2312874f3 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Jul 30, 2026

To disclose

—

Affected

Not disclosed

Linked

5 filings

Confidence

69%

Full breach record for River Financial Corporation →

River Financial Corporation filed a supplemental 8-K (Item 1.05) regarding a cybersecurity incident. The company determined an unauthorized threat actor accessed its network and exfiltrated data. The full scope and nature of the information (including PII) are undetermined. River attempted to suppress data by obtaining representations from the threat actor that it deleted the data. The incident is ongoing and materiality is not yet determined.

J jump to incidentP pin to compareR raw source

SEC clockMateriality determined Jun 19, 2026 → Filed Jul 30, 202641d ✗ SEC 4-day late

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline — partial

? — ?

Breach window unknown

Jul 30, 2026

Filed

No interval is drawn: no breach start or discovery date is on record for this filing.

This filing is one of 5 filings about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

SEC 8-Kbd_994819586d228b3b2026-07-17 · +13dVerified by operator
SEC 8-Kbd_5003c9d941db0a9c2026-07-10 · +20dVerified by operator
SEC 8-Kbd_712200f8a5f0b33a2026-07-06 · +24dVerified by operator
SEC 8-Kbd_b49f2a1e760cb3ea2026-06-25 · +35dCandidate

Name: River Financial Corporation
norm: river financial
SEC CIK: 0001641601

Name: River Financial Corporation
norm: river financial
SEC CIK: 0001641601
Industry: Financial Servicesllm

Discovered: —
Materiality determined: Jun 19, 2026
Notification sent: Jul 30, 2026
Affected individuals: Not disclosed
Data types: PII
Attack vector: Unauthorized Access
MITRE ATT&CK: T1041 Exfiltration Over C2 Channel
Threat actor: External

During the incident: River took steps to attempt to suppress the affected data, including obtaining representations from the threat actor that it deleted the data in its possession
Source: Quoted from the filing itself, not independently verified.

Compliance flags: SEC 4-day late · 41d
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
Clock breakdown: Statute Window Elapsed Threshold Status
SEC
Materiality determined: Jun 19, 2026
→ Filed: Jul 30, 2026
41d cal. 4 business days SEC 4-day late

Statute	Window	Elapsed	Threshold	Status
SEC	Materiality determined: Jun 19, 2026 → Filed: Jul 30, 2026	41d cal.	4 business days	SEC 4-day late

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings

View merged incident ↗

SEC 8-KJun 25 · first

SEC 8-K+11d

SEC 8-K+15d

SEC 8-K+22d

SEC 8-K+35d · this page

Pattern: first filing Jun 25, last Jul 30 — a 35-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

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

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statementThis record

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

Source URL: https://www.sec.gov/Archives/edgar/data/1641601/000119312526325324/ck0001641601-20260619.htm
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Jul 30, 2026
Raw hash: a55120d4fcce8d47642adc9d10572bf7b844f7c7dbb0c5dab821d21d91057cf3

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html51.4 KB

Download View at source

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityRiver Financial Corporation

Victim entityRiver Financial Corporation

IncidentUnauthorized Access

Stated responseRiver took steps to attempt to suppress the affected data, including obtaining representations from the threat actor that it deleted the data in its possession

ComplianceSEC 4-day late

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing