DisclosureLens
Leak SiteState AGConfirmed3 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedplayhigh sensitivity
Merged incident · 3 filings

Darvin Furniture — October 2025 breach

Clustered 3 filings across 3 jurisdictions · filing window Oct 25, 2025 Nov 26, 2025. View entity profile → Other incidents for this victim →

affected count agreeMerge100%

Determination

Confirmed

Members

3 filings

States

2

Affected · reported

2,280

First → last filing

Oct 25, 2025 Nov 26, 2025

Merge confidence

100%

incident inc_80d7a1753b39439a · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings and 1 unverified claim. Intrusion Oct 30, 2025, discovered Oct 30, 2025 — the first regulatory filing landed 2 days later. 2,280 individuals reported across the linked filings. Data reported: Government ID. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
2days

Discovered → first regulatory filing

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

Filing span
32days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delayno SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksLeak gap Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 30, 2025breach begins
Oct 30, 2025discovered
notification delay · 2 days
Nov 1, 2025first filing
Nov 26, 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. OCT 25Leak siteplay postfirst filing · attacker claim · unverifiedday 0
  2. NOV 1IL AGIL AG noticeno count stated+7d
  3. NOV 26IN AGIN AG noticemost recent · states nationwide total 2,280+32d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 30, 2025
IN AG
Discovered
Oct 30, 2025
IL AG
Data types
Government ID
IL 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)

2,280

Sum of filed state slices

84· 3.7% of stated

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

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 filing2 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 Aug 25, 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

32 days

Cadence

~1 / 16d

vs. multi-state median

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