Coty, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2018-07-06. The breach occurred from 1/12/2018 to 2/8/2018. 6 Montana residents were affected.
Affected (this filing): 6
Clustered 2 filings across 2 jurisdictions · filed Jul 6, 2018. View entity profile → Other incidents for this victim →
incident inc_573edf1e39f946e7 · 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
Jan 12, 2018
When the intrusion reportedly occurred, per the linked filings
Jan 12, 2018
Reported by CALIFORNIA AG filing
Coty, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2018-07-06. The breach occurred from 1/12/2018 to 2/8/2018. 6 Montana residents were affected.
Affected (this filing): 6
Coty, Inc. disclosed that hackers used phishing techniques to access employee email accounts in January and February 2018. The company became aware of the incident on January 12, 2018. The attackers primarily targeted corporate financial information, but personal details of customers and employees may have been exposed. Coty contained the incident, reset passwords, enhanced email security processes, and engaged forensic experts. Credit monitoring services were offered to affected individuals.
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.