DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed6 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedkarakurthigh sensitivity
Merged incident · 6 records

York County School of Technology — March 2023 breach

Clustered 6 records across 5 jurisdictions: 5 filings and 1 leak-site claim · filing window Apr 4, 2024 → Apr 8, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 records

States

5

Affected · reported

30,914

First → last filing

Apr 4, 2024 → Apr 8, 2024

Merge confidence

100%

incident inc_9f12e88b116b4c85 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 27, 2023–Apr 26, 2023, discovered Mar 27, 2023 — the first regulatory filing landed 374 days later. 30,914 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
374days

Discovered → first regulatory filing

Discovery variance
354days

Range of discovered_at dates across filings

Leak precedence
325days before filing

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

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 >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 27, 2023breach begins
Mar 27, 2023discovered · members disagree
notification delay · 374 days
Apr 4, 2024first filing
Apr 8, 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. MAY 15Leak sitekarakurt postfirst record · attacker claim · unverifiedday 0
  2. APR 4MA AGMA AG notice15 MA residents+325d
  3. APR 4ME AGME AG noticestates nationwide total 30,914+325d
  4. APR 5IN AGIN AG noticestates nationwide total 30,914+326d
  5. APR 5VT AGVT AG noticeno count stated+326d
  6. APR 8NH AGNH AG noticemost recent · 1 NH residents+329d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 27, 2023
ME AG
Discovered
Mar 27, 2023NH AGMar 15, 2024ME AGfilings disagree on discovery
Data types
Credentials · Health (basic) · Identity (basic) · Government ID
MA AG + ME 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)

30,914

Sum of filed state slices

20· 0.1% of stated

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

US30,914
MA15
IN3
ME1
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 report

No press coverage linked yet.

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

4 days

Cadence

~1 / 1d

vs. multi-state median

1.5× faster

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.