Fitzgerald Auto Malls reported a data breach to the Montana Attorney General. The breach was reported on 2025-04-25. The breach occurred on 02/04/2024. 36 Montana residents were affected.
Affected (this filing): 36
Clustered 2 filings across 2 jurisdictions · filed Apr 25, 2025. View entity profile → Other incidents for this victim →
incident inc_9ed3db09fe674c6d · 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.
DE MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 4, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 4, 2024
Reported by DELAWARE AG filing
Fitzgerald Auto Malls reported a data breach to the Montana Attorney General. The breach was reported on 2025-04-25. The breach occurred on 02/04/2024. 36 Montana residents were affected.
Affected (this filing): 36
Fitzgerald Auto Malls (JJF Management) notified affected individuals of a cybersecurity incident detected on February 4, 2024, involving unauthorized access to its network. The incident exposed personal information, including names. The company engaged external forensic investigators, secured its network, and implemented security improvements recommended by third-party experts. Affected individuals were offered complimentary credit monitoring and fraud assistance services through Cyberscout (a TransUnion company). The notification was sent on April 24, 2025.
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.