DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed10 records · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced8basehigh sensitivity
Merged incident · 10 records

Trustees of Thayer Academy — January 2023 breach

Clustered 10 records across 7 jurisdictions: 9 filings and 1 leak-site claim · filing window Apr 4, 2023 → May 17, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

7

Affected · reported

15,223

First → last filing

Apr 4, 2023 → May 17, 2024

Merge confidence

100%

incident inc_aadce74f2b984f7d · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 19, 2023–Feb 4, 2023, discovered Feb 4, 2023 — the first regulatory filing landed 59 days later. 15,223 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 409-day schedule across 9 filings beginning Apr 4, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
443days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 49d

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
409days

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 >180dVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 19, 2023breach begins
Feb 4, 2023discovered · members disagree
notification delay · 59 days
Apr 4, 2023first filing
May 17, 2024most recent filing

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

Member cascade — every filing and leak-site claim in this incident

  1. FEB 7Leak site8base postfirst record · attacker claim · unverifiedday 0
  2. APR 4VT AGVT AG noticeno count stated+56d
  3. APR 5MA AGMA AG notice439 MA residents+57d
  4. APR 10NH AGNH AG notice2 NH residents+62d
  5. MAY 14VT AGVT AG noticeno count stated+462d
  6. MAY 14ME AGME AG notice148 affected+462d
  7. MAY 14IN AGIN AG noticestates nationwide total 15,223+462d
  8. MAY 14CA AGCA AG noticeno count stated+462d
  9. MAY 14MT AGMT AG notice11 MT residents+462d
  10. MAY 17NH AGNH AG noticemost recent · 229 NH residents+465d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 4, 2023
ME AG
Discovered
Feb 4, 2023VT AG + NH AG + MT AGApr 22, 2024ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
VT AG + NH AG + ME 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,223

Sum of filed state slices

908· 6.0% of stated

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

US15,223
MA439
NH229
ME148
IN81
MT11

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 filing9 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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

409 days

Cadence

~1 / 51.1d

vs. multi-state median

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