Hanon Systems USA LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-09-04. The breach occurred on 7/21/2024. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Sep 4, 2024. View entity profile → Other incidents for this victim →
incident inc_9a36a6c5ef664881 · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 21, 2024
When the intrusion reportedly occurred, per the linked filings
Jul 21, 2024
Reported by MAINE AG filing
Hanon Systems USA LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-09-04. The breach occurred on 7/21/2024. 1 Montana residents were affected.
Affected (this filing): 1
On July 21, 2024, Hanon Systems USA, LLC experienced a ransomware event in which a third-party threat actor accessed certain systems and held data under threat of ransom demand. Affected information included names, contact information, and Social Security Numbers of current and former employees. One Maine resident was among the 1,205 total individuals affected. Consumer notification was sent on September 4, 2024. Equifax 1B Gold credit monitoring was offered for 12 months.
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.