Speakman Financial Group reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-08 and was reported on 2025-08-12. 1 Indiana residents were affected. 991 individuals affected in total.
Affected (this filing): 991
Clustered 2 filings across 2 jurisdictions · filing window Aug 12, 2025 → Aug 13, 2025. View entity profile → Other incidents for this victim →
incident inc_958168d10fb34d7c · 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.
PII · Financial · Government ID
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 8, 2025
When the intrusion reportedly occurred, per the linked filings
Jul 8, 2025
Reported by MAINE AG filing
Speakman Financial Group reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-08 and was reported on 2025-08-12. 1 Indiana residents were affected. 991 individuals affected in total.
Affected (this filing): 991
On July 8, 2025, Speakman Financial Group discovered an unknown party had accessed its computer systems via a malicious email attachment. The incident was determined to be the result of a phishing/malicious attachment. Affected data included client names, addresses, account numbers, and potentially social security numbers. 991 total individuals were affected, including 3 Maine residents. Notification letters were sent August 12, 2025, and 12-month IDX identity protection services were offered.
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.