DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SitePressState AGConfirmed8 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedrhysidahigh sensitivity
Merged incident · 8 filings

Prince George's County Public Schools — August 2023 breach

Clustered 8 filings across 6 jurisdictions · filing window Aug 14, 2023 → Feb 26, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

5

Affected · reported

99,543

First → last filing

Aug 14, 2023 → Feb 26, 2024

Merge confidence

100%

incident inc_68a167c2c0be46cd · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings, 1 press report and 2 unverified claims. Intrusion Aug 3, 2023–Aug 14, 2023, discovered Aug 14, 2023 — the first regulatory filing landed 184 days later (flagged late). 99,543 individuals reported across the linked filings. Data reported: Government ID, Financial account, Credentials, and 3 more. Notifications rolled out on a 196-day schedule across 5 filings beginning Aug 14, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
184days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
184days 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
196days

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 >180dMaine✗ ME AG >90d · 186dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 3, 2023breach begins
Aug 14, 2023discovered
notification delay · 184 days
Feb 14, 2024first filing
Feb 26, 2024most 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. AUG 14Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. AUG 25Leak siterhysida postattacker claim · unverified+11d
  3. FEB 14IN AGIN AG noticestates nationwide total 99,543+184d
  4. FEB 16ME AGME AG noticestates nationwide total 99+186d
  5. FEB 16VT AGVT AG noticeno count stated+186d
  6. FEB 16MA AGMA AG notice49 MA residents+186d
  7. FEB 26NH AGNH AG noticemost recent · 4 NH residents+196d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 3, 2023
IN AG
Discovered
Aug 14, 2023· 11d undetected
ME AG + VT AG + NH AG
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PII
ME AG + MA 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)

99,543

Sum of filed state slices

100· 0.1% of stated

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

US99,543
MA49
IN35
ME12
NH4

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

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

196 days

Cadence

~1 / 28d

vs. multi-state median

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