Hoist & Crane Service Group reported a data breach to the Montana Attorney General. The breach was reported on 2022-05-12. The breach occurred on 9/25/2021. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filing window May 12, 2022 → May 14, 2022. View entity profile → Other incidents for this victim →
incident inc_ac5bae685df1462e · merge_method human · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 25, 2021
When the intrusion reportedly occurred, per the linked filings
Apr 13, 2022
Reported by MAINE AG filing
Hoist & Crane Service Group reported a data breach to the Montana Attorney General. The breach was reported on 2022-05-12. The breach occurred on 9/25/2021. 3 Montana residents were affected.
Affected (this filing): 3
Hoist & Crane Service Group reported a data breach affecting 16 Maine residents. The breach, which occurred on September 25, 2021, and was discovered on April 13, 2022, was described as an external system breach or hacking incident. The compromised information included names and Social Security Numbers. The company provided written notification to the affected individuals on May 12, 2022, and offered 12 months of credit monitoring and identity protection services through IDX.
Affected (this filing): 16
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.