McAdam Financial Group reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-16 and was reported on 2025-10-09. 1 Indiana residents were affected. 101 individuals affected in total.
Affected (this filing): 101
Clustered 2 filings across 2 jurisdictions · filed Oct 9, 2025. View entity profile → Other incidents for this victim →
incident inc_1152c8e806034b35 · 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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 16, 2025
When the intrusion reportedly occurred, per the linked filings
Jul 16, 2025
Reported by NEW HAMPSHIRE AG filing
McAdam Financial Group reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-16 and was reported on 2025-10-09. 1 Indiana residents were affected. 101 individuals affected in total.
Affected (this filing): 101
McAdam Financial Group reported an unauthorized access to an email account on July 16, 2025, affecting one New Hampshire resident. The incident involved phishing leading to credential compromise. Impacted data included name, SSN, and financial account information. Notification was sent to the NH Attorney General and the affected individual on October 9, 2025.
Affected (this filing): 1
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.