GLOBALClaimed by Black BastaFirst sightinglinked via shared-victim match · 100%
Posted to leak site Nov 16, 2022bd_a4604076e0358419
Clustered 4 filings across 4 jurisdictions · filing window Nov 16, 2022 → Jul 6, 2023. View entity profile → Other incidents for this victim →
incident inc_a18cd2a5b17d4a04 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Government ID
CA ME MT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 19, 2022
When the intrusion reportedly occurred, per the linked filings
Oct 19, 2022
Reported by CALIFORNIA AG filing
Mar 10, 2023
Reported by MAINE AG filing
IMA Financial Group, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-04-20. The breach occurred on 10/19/2022. 91 Montana residents were affected.
Affected (this filing):
IMA Financial Group, Inc. reported a data security incident where unauthorized access occurred between October 18-19, 2022. The company discovered unusual activity on October 19, 2022, and engaged external cybersecurity experts. The incident potentially affected personal information of individuals associated with current or former employers. IMA implemented additional network safeguards and offered complimentary credit monitoring and identity protection services through IDX.
IMA Financial Group, Inc. reported an external hacking incident that occurred between October 18 and October 19, 2022. The breach was discovered on March 10, 2023, and affected 75 Maine residents. The compromised information included names combined with Driver's License or Non-Driver Identification Card Numbers. In response, the company offered 12 months of credit monitoring, identity protection, and restoration services.
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.
Affected (this filing): 75