DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed12 records · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedtermitehigh sensitivity
Merged incident · 12 records

News-Press and Gazette Co. — September 2025 breach

Clustered 12 records across 7 jurisdictions: 7 filings and 5 leak-site claims · filing window Dec 17, 2025 → Dec 22, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 records

States

7

Affected · reported

11,440

First → last filing

Dec 17, 2025 → Dec 22, 2025

Merge confidence

100%

incident inc_d20382e5e928455c · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 5 unverified claims. The filings describe unauthorized access. Intrusion Sep 2, 2025–Sep 25, 2025, discovered Sep 4, 2025 — the first regulatory filing landed 104 days later (flagged late). 11,440 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 5-day schedule across 7 filings beginning Dec 17, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
104days

Discovered → first regulatory filing

Discovery variance
74days

Range of discovered_at dates across filings

Leak precedence
92days 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
5days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 2, 2025breach begins
Sep 4, 2025discovered · members disagree
notification delay · 104 days
Dec 17, 2025first filing
Dec 22, 2025most 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. SEP 16Leak sitetermite postfirst record · attacker claim · unverifiedday 0
  2. SEP 26Leak sitetermite postattacker claim · unverified+10d
  3. SEP 26Leak sitetermite postattacker claim · unverified+11d
  4. SEP 26Leak sitetermite postattacker claim · unverified+11d
  5. SEP 29Leak sitetermite postattacker claim · unverified+14d
  6. DEC 17MA AGMA AG notice22 MA residents+92d
  7. DEC 17TX AGTX AG noticestates nationwide total 11,440+92d
  8. DEC 17CA AGCA AG noticeno count stated+92d
  9. DEC 17OR AGOR AG noticestates nationwide total 11,440+92d
  10. DEC 17IN AGIN AG noticestates nationwide total 11,440+92d
  11. DEC 17WA AGWA AG notice47 WA residents+92d
  12. DEC 22NH AGNH AG noticemost recent · 8 NH residents+97d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 2, 2025 – Sep 25, 2025
TX AG
Discovered
Sep 4, 2025OR AG + NH AGNov 17, 2025TX AG + WA AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
MA AG + TX AG + NH AG +2
Attack vector
Unauthorized Access
WA 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)

11,440

Sum of filed state slices

670· 5.9% of stated

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

US11,440
TX531
IN62
WA47
MA22
NH8

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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 Oct 29, 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

5 days

Cadence

~1 / 0.8d

vs. multi-state median

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