DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Moody Bible Institute — June 2026 breach

Clustered 10 filings across 10 jurisdictions · filing window Jul 1, 2026 → Aug 4, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

155,226

First → last filing

Jul 1, 2026 → Aug 4, 2026

Merge confidence

100%

incident inc_cb7041f2a4574b78 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Jun 12, 2026, discovered Jun 12, 2026 — the first regulatory filing landed 19 days later (flagged late). 155,226 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 34-day schedule across 10 filings beginning Jul 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
19days

Discovered → first regulatory filing

Discovery variance
11days

Range of discovered_at dates across filings

Filing span
34days

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 clocksOregon✗ OR AG >45dWashington⏱ WA AG >30dMassachusetts⏱ MA AG >30dIowa✓ IA AG ≤5 bdaySouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 12, 2026breach begins
Jun 12, 2026discovered · members disagree
notification delay · 19 days
Jul 1, 2026first filing
Aug 4, 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. JUL 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 23WA AGWA AG notice8,955 WA residents+22d
  3. JUL 23CA AGCA AG noticeno count stated+22d
  4. JUL 31NH AGNH AG notice447 NH residents+30d
  5. JUL 31IA AGIA AG notice2,200 IA residents+30d
  6. JUL 31NE AGNE AG noticeno count stated+30d
  7. JUL 31MA AGMA AG notice942 MA residents+30d
  8. JUL 31OR AGOR AG noticestates nationwide total 155,226+30d
  9. JUL 31SC AGSC AG notice1,098 SC residents+30d
  10. AUG 4TX AGTX AG noticemost recent · states nationwide total 155,226+34d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 12, 2026
WA AG
Discovered
Jun 12, 2026WA AG + CA AG + NH AG +5Jun 23, 2026IL AG + TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
IL AG + WA AG + NH AG +6
Attack vector
Unauthorized Access
WA AG

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)

155,226

Sum of filed state slices

19,281· 12.4% of stated

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

US155,226
WA8,955
TX5,639
IA2,200
SC1,098
MA942
NH447

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

34 days

Cadence

~1 / 3.8d

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.