King City Lumber — November 2025 breach
One linked filing — more sources may join as they report · filed Mar 31, 2026. View entity profile → Other incidents for this victim →
incident inc_e3d972c030e14d0a · merged by deterministic
Litigation Timing
Discovered → first regulatory filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- MAR 31NE AGNE AG noticeonly filing · no count statedday 0
- 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
- Response
- Began an investigation into the scope and nature of the suspicious activity · Retained legal counsel and third-party forensic specialists to investigate the unusual activity · Began a comprehensive review of the data set to determine what sensitive and/or personal information was impacted 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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.