Confirmed breach. Intrusion Sep 9, 2024, discovered Dec 2, 2024 — the first regulatory filing landed 29 days later. 458 individuals reported across the linked filings.
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.
Regulatory clocksMaine✓ ME AG ≤30d · 29dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
458
Data types
1
PII
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 9, 2024
When the intrusion reportedly occurred, per the linked filings
LBX Company LLC (Lexington, KY) reported an inadvertent disclosure breach that occurred on September 9, 2024 and was discovered on December 2, 2024. A total of 458 individuals were affected, including 50 Maine residents. Notification was sent on December 31, 2024. Experian credit monitoring was offered for 12 months to affected individuals.
Affected (this filing): 50
ME AG ≤30d · 29d
🏎️Indiana State AGMost recentlinked via multistate filing link · 100%
LBX Company LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-09 and was reported on 2024-12-31. 3 Indiana residents were affected. 458 individuals affected in total.
Affected (this filing): 458
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.