GAIN Capital Group, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-06-22. The breach occurred from 4/14/2020 to 4/18/2020. 27 Montana residents were affected.
Affected (this filing): 27
Clustered 2 filings across 2 jurisdictions · filed Jun 22, 2020. View entity profile → Other incidents for this victim →
incident inc_50e48a4d80e74501 · 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
Apr 14, 2020
When the intrusion reportedly occurred, per the linked filings
Apr 15, 2020
Reported by CALIFORNIA AG filing
GAIN Capital Group, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-06-22. The breach occurred from 4/14/2020 to 4/18/2020. 27 Montana residents were affected.
Affected (this filing): 27
GAIN Capital Group, LLC reported a data breach affecting current and former customers. Unauthorized access occurred between April 14 and 18, 2020, discovered on April 15, 2020. The incident involved suspicious login activity leading to server access. Customer names and additional personal data were potentially accessed, but Social Security numbers were not involved. GAIN engaged a cybersecurity firm, secured and took servers offline, and implemented enhanced monitoring.
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.