Utility Trailer Manufacturing Company reported a data breach to the Montana Attorney General. The breach was reported on 2022-02-11. The breach occurred from 4/5/2021 to 4/25/2021. 5 Montana residents were affected.
Affected (this filing): 5
Clustered 2 filings across 2 jurisdictions · filed Feb 11, 2022. View entity profile → Other incidents for this victim →
incident inc_30a64b4c9d2e40f6 · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 5, 2021
When the intrusion reportedly occurred, per the linked filings
Apr 25, 2021
Reported by CALIFORNIA AG filing
Utility Trailer Manufacturing Company reported a data breach to the Montana Attorney General. The breach was reported on 2022-02-11. The breach occurred from 4/5/2021 to 4/25/2021. 5 Montana residents were affected.
Affected (this filing): 5
Utility Trailer Manufacturing Company reported a cybersecurity incident occurring between April 5 and April 25, 2021, where an unknown actor accessed computer systems. The breach was discovered on April 25, 2021, and notification to affected individuals was sent around November 23, 2021. The incident involved unauthorized access to systems containing names and addresses. The company reported the incident to federal law enforcement, offered 12 months of credit monitoring via Experian, and is reviewing security policies.
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.