Confirmed breach. Intrusion Aug 7, 2024, discovered Aug 21, 2024 — the first regulatory filing landed 172 days later (flagged late). 3,248 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 claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
3,248
Data types
3
Identity (basic) · Government ID · PII
Jurisdictions
2
IN MD
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 7, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Aug 21, 2024
Reported by MARYLAND AG filing
172 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Commercial Specialty Truck Holdings reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-07 and was reported on 2025-02-09. 4 Indiana residents were affected. 3,248 individuals affected in total.
Commercial Specialty Truck Holdings notified Maryland AG of unauthorized access to files containing names, SSNs, and health insurance numbers for 2 Maryland residents. Incident occurred Aug 7, 2024; discovered Aug 21, 2024. Notification sent Feb 11, 2025. Remediation includes credit monitoring via Kroll and system security enhancements.
Affected (this filing): 2
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.