DisclosureLens
State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

Lycoming County, Pennsylvania (the “County”) — August 2025 breach

Clustered 5 filings across 5 jurisdictions · filing window Dec 9, 2025 Dec 16, 2025. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

1,876

First → last filing

Dec 9, 2025 Dec 16, 2025

Merge confidence

100%

incident inc_a650824926e44b14 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a ransomware attack. Intrusion Aug 11, 2025–Aug 12, 2025, discovered Aug 12, 2025 — the first regulatory filing landed 119 days later (flagged late). 1,876 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 7-day schedule across 5 filings beginning Dec 9, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
119days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
7days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >90d · 119dMassachusetts MA credit monitoring dueFull clock table in Litigation Timeline

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.

Lycoming County, Pennsylvania (the “County”) data breach (2025) · DisclosureLens