Diamond Select Toys & Collectibles, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-07-13. The breach occurred from 10/23/2021 to 10/25/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Jul 13, 2022. View entity profile → Other incidents for this victim →
incident inc_c991237f3c444f06 · merge_method llm · confidence 44%
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.
Financial account · Financial credentials · Identity (basic)
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 23, 2021
When the intrusion reportedly occurred, per the linked filings
Feb 25, 2022
Reported by MAINE AG filing
Diamond Select Toys & Collectibles, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-07-13. The breach occurred from 10/23/2021 to 10/25/2021. 1 Montana residents were affected.
Affected (this filing): 1
Diamond Select Toys & Collectibles, LLC reported a data breach affecting 3 Maine residents. The breach, which occurred from October 23, 2021, to October 25, 2021, was discovered on February 25, 2022. The incident was described as an external system breach (hacking) and involved the compromise of names or other personal identifiers in combination with financial account numbers or credit/debit card numbers, including their security codes, access codes, passwords, or PINs. Affected individuals were notified in writing on July 8, 2022.
Affected (this filing): 3
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.