Confirmed breach. Intrusion Feb 4, 2024, discovered Feb 4, 2024 — the first regulatory filing landed 446 days later (flagged late). 381,679 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 clocksVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
381,679
Data types
1
Identity (basic)
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 4, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Feb 4, 2024
Reported by VERMONT AG filing
446 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
JJF Management dba Fitzgerald Auto Malls reported a data breach to the Indiana Attorney General. The breach occurred on 2024-02-04 and was reported on 2025-04-25. 166 Indiana residents were affected. 381,679 individuals affected in total.
JJF Management dba Fitzgerald Auto Malls notified Vermont consumers of a cybersecurity incident detected on February 4, 2024. Unauthorized access resulted in the exposure of personal information, including names. The company engaged external forensic investigators, secured its network, and offered complimentary credit monitoring services to affected individuals.
VT AG >45 bday
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.