Aladdin Capital reported a data breach to the Montana Attorney General. The breach was reported on 2021-09-27. The breach occurred from 11/18/2020 to 11/24/2020. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filed Sep 27, 2021. View entity profile → Other incidents for this victim →
incident inc_f1e2ed5bf1734b88 · 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
Nov 18, 2020
When the intrusion reportedly occurred, per the linked filings
Nov 24, 2020
Reported by MAINE AG filing
Aladdin Capital reported a data breach to the Montana Attorney General. The breach was reported on 2021-09-27. The breach occurred from 11/18/2020 to 11/24/2020. 3 Montana residents were affected.
Affected (this filing): 3
Financial services firm Aladdin Capital experienced an external system breach on November 18, 2020, which was discovered on November 24, 2020. The breach affected 2,318 individuals, compromising names and driver's license or non-driver identification card numbers. The company notified affected individuals on September 27, 2021, and offered 12 months of credit monitoring and identity theft restoration services through TransUnion.
Affected (this filing): 2,318
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.