DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed9 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedfoghigh sensitivity
Merged incident · 9 filings

Asbury Theological Seminary — June 2024 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

15,560

First → last filing

Mar 10, 2024 → Mar 14, 2025

Merge confidence

100%

incident inc_be66e2fd3043409d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jun 1, 2024–Jun 6, 2024, discovered Jun 6, 2024. 15,560 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 369-day schedule across 8 filings beginning Mar 10, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
258days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 106d

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

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dMaryland✗ MD AG >90dMaine✗ ME AG >90d · 277dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 1, 2024breach begins
Jun 6, 2024discovered · members disagree
Mar 10, 2024first filing
Mar 14, 2025most 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. MAR 10VT AGVT AG noticefirst filing · no count statedday 0
  2. JUN 24Leak sitefog postattacker claim · unverified+106d
  3. MAR 10IN AGIN AG noticestates nationwide total 15,560+365d
  4. MAR 10MT AGMT AG notice16 MT residents+365d
  5. MAR 10MD AGMD AG noticeno count stated+365d
  6. MAR 10NE AGNE AG noticeno count stated+365d
  7. MAR 10ME AGME AG noticestates nationwide total 15,560+365d
  8. MAR 11MA AGMA AG notice55 MA residents+366d
  9. MAR 14NH AGNH AG noticemost recent · 22 NH residents+369d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 1, 2024 – Jun 6, 2024
VT AG
Discovered
Jun 6, 2024MT AG + MD AG + ME AG +1Feb 19, 2025NE AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
VT AG + MT AG + MD AG +3
Attack vector
Unauthorized Access
VT 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)

15,560

Sum of filed state slices

746· 4.8% of stated

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

US15,560
IN631
MA55
ME22
NH22
MT16

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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing8 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
Reviewed
operator-reviewed Aug 23, 2026 · 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

369 days

Cadence

~1 / 46.1d

vs. multi-state median

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