DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteSEC 8-KState AGConfirmed14 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilinhigh sensitivity
Merged incident · 14 filings

Lee Enterprises, Incorporated — February 2025 breach

Clustered 14 filings across 12 jurisdictions · filing window Feb 3, 2025 → Jun 5, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

11

Affected · reported

39,779

First → last filing

Feb 3, 2025 → Jun 5, 2025

Merge confidence

100%

incident inc_8a2ed1f527e94d0b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 2 unverified claims. Intrusion Feb 1, 2025–Feb 3, 2025, discovered Feb 3, 2025 — the first regulatory filing landed 15 days later (flagged late). 39,779 individuals reported across the linked filings. Data reported: Government ID, Health (basic), PII, and 1 more. Notifications rolled out on a 122-day schedule across 12 filings beginning Feb 3, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
15days

Discovered → first regulatory filing

Discovery variance
114days

Range of discovered_at dates across filings

Leak precedence
15days 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.

Materiality delta
9days

Discovery to SEC materiality determination

SEC filing delay
6days

Materiality determination to SEC 8-K filing

Filing span
122days

Time between earliest and latest filing

Regulatory clocksSEC✗ SEC 4-day late · 20dMaine✗ ME AG >90d · 120dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 120dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 1, 2025breach begins
Feb 3, 2025discovered · members disagree
notification delay · 15 days
Feb 18, 2025first filing
Jun 5, 2025most 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. FEB 3Leak siteqilin postfirst filing · attacker claim · unverifiedday 0
  2. FEB 18SEC 8-KSEC 8-K noticeno count stated+15d
  3. FEB 27Leak siteqilin postattacker claim · unverified+24d
  4. MAR 6SEC 8-KSEC 8-K noticeno count stated+31d
  5. JUN 1IL AGIL AG noticeno count stated+118d
  6. JUN 3MT AGMT AG notice1,542 MT residents+120d
  7. JUN 3NE AGNE AG notice3,354 NE residents+120d
  8. JUN 3ME AGME AG noticestates nationwide total 39,779+120d
  9. JUN 3VT AGVT AG noticeno count stated+120d
  10. JUN 3NH AGNH AG notice17 NH residents+120d
  11. JUN 4OR AGOR AG noticestates nationwide total 39,779+121d
  12. JUN 4CA AGCA AG noticeno count stated+121d
  13. JUN 4MA AGMA AG notice55 MA residents+121d
  14. JUN 5TX AGTX AG noticemost recent · states nationwide total 39,779+122d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 3, 2025
SEC 8-K
Discovered
Feb 3, 2025SEC 8-K + IL AG + NE AG +4May 28, 2025MT AG + OR AG + TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PII
IL AG + NE AG + ME AG +6
Attack vector
Ransomware
SEC 8-K

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)

39,779

Sum of filed state slices

5,967· 15.0% of stated

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

US39,779
NE3,354
MT1,542
TX986
MA55
NH17
ME13

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 report

No press coverage linked yet.

State AG / regulator filing10 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement2 members

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

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

122 days

Cadence

~1 / 9.4d

vs. multi-state median

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