HEXPOL Holding Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-12-22 and was reported on 2025-07-03. 1 Indiana residents were affected. 1,723 individuals affected in total.
Affected (this filing): 1,723
Clustered 2 filings across 2 jurisdictions · filing window Jul 3, 2025 → Jul 8, 2025. View entity profile → Other incidents for this victim →
incident inc_c02bab38f0cb46fa · 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.
PII
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 22, 2024
When the intrusion reportedly occurred, per the linked filings
Dec 22, 2024
Reported by MAINE AG filing
HEXPOL Holding Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-12-22 and was reported on 2025-07-03. 1 Indiana residents were affected. 1,723 individuals affected in total.
Affected (this filing): 1,723
On December 22, 2024, HEXPOL Compounding Americas detected unauthorized access to its network. An investigation revealed that an unauthorized actor may have copied certain files from the network. The scope of impacted personal information was confirmed on June 25, 2025 after extensive manual review. One Maine resident was affected out of 1,723 total individuals. Affected individuals were offered 24-month Experian IdentityWorks credit monitoring and identity restoration services.
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.