BYU-Pathway — June 2025 breach

Clustered 9 filings across 9 jurisdictions · filing window Jul 14, 2025 → Jul 22, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

Affected · reported

25,136

First → last filing

Jul 14, 2025 → Jul 22, 2025

Merge confidence

100%

incident inc_ce0f26f1d6404286 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe a third-party compromise. Intrusion Jun 17, 2025–Jun 24, 2025, discovered Jun 17, 2025 — the first regulatory filing landed 27 days later. 25,136 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Education, and 1 more. Notifications rolled out on a 8-day schedule across 9 filings beginning Jul 14, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

27days

Discovered → first regulatory filing

Discovery variance

7days

Range of discovered_at dates across filings

Filing span

8days

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 clocksWashington✓ WA AG ≤30dCalifornia✓ CA 60-day OK · 27dMaine✓ ME AG ≤30d · 24dMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤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.