DisclosureLens
Leak SiteState AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcloakhigh sensitivity
Merged incident · 7 filings

Abilene Independent School District (Abilene ISD) — June 2024 breach

Clustered 7 filings across 7 jurisdictions · filing window Jul 4, 2024 Nov 15, 2024. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

16,181

First → last filing

Jul 4, 2024 Nov 15, 2024

Merge confidence

100%

incident inc_d9b2ffd010f74a50 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jun 8, 2024–Jun 9, 2024, discovered Jun 9, 2024 — the first regulatory filing landed 159 days later (flagged late). 16,181 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 133-day schedule across 6 filings beginning Jul 4, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
159days

Discovered → first regulatory filing

Discovery variance
130days

Range of discovered_at dates across filings

Leak precedence
133days before filing

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

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksVermont VT AG >45 bdayLeak gap Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 8, 2024breach begins
Jun 9, 2024discovered · members disagree
notification delay · 159 days
Nov 15, 2024first filing
watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 4Leak sitecloak postfirst filing · attacker claim · unverifiedday 0
  2. NOV 15VT AGVT AG noticeno count stated+133d
  3. NOV 15NH AGNH AG notice2 NH residents+133d
  4. NOV 15MA AGMA AG notice5 MA residents+133d
  5. NOV 15ME AGME AG noticestates nationwide total 16,181+133d
  6. NOV 15MT AGMT AG notice2 MT residents+133d
  7. NOV 15IN AGIN AG noticemost recent · states nationwide total 16,181+133d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 9, 2024
NH AG
Discovered
Jun 9, 2024VT AG + MT AGOct 17, 2024ME AGfilings disagree on discovery
Data types
Education · Identity (basic) · Government ID · PII
VT AG + NH AG + ME AG +2
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)

16,181

Sum of filed state slices

21· 0.1% of stated

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

US16,181
IN10
MA5
NH2
ME2
MT2

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

133 days

Cadence

~1 / 22.2d

vs. multi-state median

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