Clustered 2 filings across 2 jurisdictions · filed Mar 15, 2024. View entity profile → Other incidents for this victim →
incident inc_9402bf02ada6474b · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Identity (basic) · Financial account · Authentication
IN VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 5, 2023
When the intrusion reportedly occurred, per the linked filings
Feb 16, 2024
Reported by VERMONT AG filing
The Biltmore Company LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2023-12-05 and was reported on 2024-03-15. 286 Indiana residents were affected. 11,530 individuals affected in total.
Affected (this filing): 11,530
The Biltmore Company, LLC notified consumers of a data breach affecting its online retail store (biltmoreshop.com). An unauthorized party inserted malicious code into the third-party hosted application, exfiltrating payment card information, names, addresses, and emails from purchases made between December 5, 2023, and February 16, 2024. The incident was contained on February 23, 2024, after engaging forensic investigators and the FBI. The company is offering 24 months of credit monitoring.
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.