DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressState AGConfirmed7 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedplayhigh sensitivity
Merged incident · 7 records

Douglas County Libraries — January 2024 breach

Clustered 7 records across 5 jurisdictions: 5 filings, 1 press report and 1 leak-site claim · filing window Mar 20, 2024 → Mar 28, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 records

States

5

Affected · reported

1,632

First → last filing

Mar 20, 2024 → Mar 28, 2024

Merge confidence

100%

incident inc_b56e114507954860 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings, 1 press report and 1 unverified claim. The filings describe a ransomware attack. Intrusion Jan 13, 2024–Jan 14, 2024, discovered Jan 14, 2024 — the first regulatory filing landed 66 days later (flagged late). 1,632 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Employment. Notifications rolled out on a 8-day schedule across 5 filings beginning Mar 20, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
66days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
43days 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
8days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 13, 2024breach begins
Jan 14, 2024discovered
notification delay · 66 days
Mar 20, 2024first filing
Mar 28, 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. JAN 14Leak siteplay postfirst record · attacker claim · unverifiedday 0
  2. MAR 20MT AGMT AG notice1 MT residents+66d
  3. MAR 20IN AGIN AG noticestates nationwide total 1,632+66d
  4. MAR 20VT AGVT AG noticeno count stated+66d
  5. MAR 20MA AGMA AG notice1 MA residents+66d
  6. MAR 28NH AGNH AG noticemost recent · 1 NH residents+74d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 13, 2024 – Jan 14, 2024
MT AG
Discovered
Jan 14, 2024· 1d undetected
MT AG + VT AG + NH AG
Data types
Employment · Identity (basic) · Government ID
MT AG + VT AG + NH AG +1
Attack vector
Ransomware
MT 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)

1,632

Sum of filed state slices

5· 0.3% of stated

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

US1,632
IN2
MT1
MA1
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
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

8 days

Cadence

~1 / 2d

vs. multi-state median

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