DisclosureLens
Leak SitePressState AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblackbytehigh sensitivity
Merged incident · 7 filings

Chambersburg Area School District — August 2023 breach

Clustered 7 filings across 6 jurisdictions · filing window Sep 7, 2023 Oct 26, 2023. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

4,265

First → last filing

Sep 7, 2023 Oct 26, 2023

Merge confidence

100%

incident inc_102c5890b2c34470 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 21, 2023–Aug 26, 2023, discovered Aug 27, 2023 — the first regulatory filing landed 60 days later. 4,265 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 60-day schedule across 5 filings beginning Sep 7, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
60days

Discovered → first regulatory filing

Discovery variance
38days

Range of discovered_at dates across filings

Leak precedence
49days 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
60days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap Leak >30dVermont VT AG >14 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 21, 2023breach begins
Aug 27, 2023discovered · members disagree
notification delay · 60 days
Oct 26, 2023first 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. SEP 7Leak siteblackbyte postfirst filing · attacker claim · unverifiedday 0
  2. OCT 26ME AGME AG noticestates nationwide total 4,265+49d
  3. OCT 26NH AGNH AG notice1 NH residents+49d
  4. OCT 26IN AGIN AG noticestates nationwide total 4,265+49d
  5. OCT 26VT AGVT AG noticeno count stated+49d
  6. OCT 26MA AGMA AG noticemost recent · 3 MA residents+49d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 21, 2023Aug 26, 2023
ME AG
Discovered
Aug 27, 2023NH AG + VT AGOct 4, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
ME AG + NH AG + VT AG +1
Attack vector
Unauthorized Access
ME 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)

4,265

Sum of filed state slices

8· 0.2% of stated

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

US4,265
MA3
ME2
IN2
NH1

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

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing5 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 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

60 days

Cadence

~1 / 10d

vs. multi-state median

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

Chambersburg Area School District data breach (2023) · DisclosureLens