Clustered 3 filings across 2 jurisdictions · filing window Jun 25, 2018 → Aug 10, 2018. View entity profile → Other incidents for this victim →
incident inc_d763518ec90a4444 · merge_method deterministic · confidence 100%
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
Sep 15, 2017 → Nov 19, 2017
When the intrusion reportedly occurred, per the linked filings
Hasbro, Inc. reported a data security breach to the California Attorney General. The incident occurred between September 15, 2017, and November 19, 2017. The provided source document contains only the filing metadata and an empty attachment placeholder; no narrative details regarding the nature of the breach, data types affected, or response actions are available in the text.
Hasbro, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2018-06-29. The breach occurred from 9/15/2017 to 9/18/2017. 1 Montana residents were affected.
Affected (this filing): 1
Jul 4, 2018
Reported by CALIFORNIA AG filing
Hasbro, Inc. disclosed unauthorized access to employee email accounts and shared network folders. The incident occurred between September 15, 2017, and November 19, 2017, and was discovered on or around July 4, 2018. Affected data may include SSNs, driver's licenses, bank account numbers, medical/health insurance info, passport numbers, and credentials. Hasbro engaged forensic experts and law enforcement.
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.