Confirmed breach. Intrusion Nov 25, 2024, discovered Nov 25, 2024 — the first regulatory filing landed 102 days later (flagged late). 205 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 clocksMaryland✗ MD AG >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
205
Data types
3
PII · PCI · Identity (basic)
Jurisdictions
2
IN MD
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 25, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Nov 25, 2024
Reported by MARYLAND AG filing
102 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Barrett-Jackson Holdings LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-11-25 and was reported on 2025-03-07. 145 Indiana residents were affected. 205 individuals affected in total.
Barrett-Jackson Holdings, LLC notified the Maryland Attorney General of a cyber incident occurring on or around November 25, 2024. The breach affected one Maryland resident, exposing their name and payment card data. The investigation is ongoing, and the company is providing 12 months of complimentary credit monitoring services to the affected individual.
Affected (this filing): 1
MD AG >90d
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.