Clustered 3 filings across 3 jurisdictions · filing window Mar 18, 2025 → Jul 30, 2025. View entity profile → Other incidents for this victim →
incident inc_3473b30b116a427e · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Financial account
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
MD NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 5, 2023 → Nov 17, 2023
When the intrusion reportedly occurred, per the linked filings
Nov 17, 2023
Reported by VERMONT AG, MARYLAND AG, NEW HAMPSHIRE AG filings
Ray Catena Motor Car Corp notified consumers of a ransomware incident occurring between Nov 5-17, 2023. Files were encrypted and data exfiltrated. Affected data includes names, SSNs, driver's licenses, health insurance info, and credentials. No identity theft detected. Credit monitoring offered.
Ray Catena Motor Car Corp. notified Maryland AG of a ransomware incident affecting 16 Maryland residents. An unknown actor gained access between Nov 5-17, 2023, encrypting files and exfiltrating data including SSNs, driver's licenses, financial accounts, credentials, and PHI. Notification sent March 18, 2025. Credit monitoring offered.
Affected (this filing): 16
Ray Catena Motor Car Corp. reported a ransomware incident to the New Hampshire AG. An unknown actor gained access to systems between Nov 5-17, 2023, encrypting files. The breach affected employee and customer data, including names, SSNs, and health insurance info. One NH resident was notified on July 30, 2025. The company engaged law enforcement, provided 12 months of credit monitoring, and enhanced security training.
Affected (this filing): 1
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.