The Biltmore Company, LLC — December 2023 breach

Clustered 7 filings across 7 jurisdictions · filing window Mar 15, 2024 → Mar 18, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

Affected · reported

11,530

First → last filing

Mar 15, 2024 → Mar 18, 2024

Merge confidence

100%

incident inc_14303fe771f249f8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe hacking. Intrusion Dec 5, 2023–Feb 16, 2024, discovered Feb 16, 2024 — the first regulatory filing landed 28 days later. 11,530 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, PII, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

28days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

3days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont⏱ VT AG >14 bdaySouth Carolina✓ SC CRA notice dueMaine✓ ME AG ≤30d · 28dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.