DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed2 records · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddragonforcelow sensitivity
Merged incident · 2 records

King City Lumber — November 2025 breach

Clustered 2 records across 1 jurisdiction: 1 filing and 1 leak-site claim · filed Mar 31, 2026. View entity profile → Other incidents for this victim →

Agreement not assessableMerge100%

Determination

Confirmed

Members

2 records

States

1

Affected · reported

—

First → last filing

Mar 31, 2026

Merge confidence

100%

incident inc_02170cdcad6243cc · merged by human · confidence 100%

Confirmed breach. The filing describes unauthorized access. Intrusion Nov 27, 2025–Dec 3, 2025, discovered Dec 3, 2025. Data reported: PII.

Litigation Timing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no SEC 8-K in this cluster; needs two dated filings.

Incident timeline

Nov 27, 2025breach begins
Dec 3, 2025discovered
Mar 31, 2026first & only filing
—watching for filings

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. DEC 5Leak sitedragonforce postfirst record · attacker claim · unverifiedday 0
  2. MAR 31NE AGNE AG noticemost recent · no count stated+115d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 27, 2025 – Dec 3, 2025
NE AG
Discovered
Dec 3, 2025· 6d undetected
NE AG
Data types
PII
NE AG
Attack vector
Unauthorized Access
NE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing1 member

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.

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.