Athlon Advisors, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-28. The breach occurred on 4/6/2023. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Aug 28, 2023 → Aug 31, 2023. View entity profile → Other incidents for this victim →
incident inc_8d7bc41541e24059 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 6, 2023
When the intrusion reportedly occurred, per the linked filings
Apr 6, 2023
Reported by NEW HAMPSHIRE AG filing
Athlon Advisors, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-28. The breach occurred on 4/6/2023. 1 Montana residents were affected.
Affected (this filing): 1
Athlon Advisors, LLC, a financial planning services provider, notified the New Hampshire Attorney General of a data security incident. On or around April 6, 2023, suspicious activity was detected in the email environment, leading to the unauthorized access of one employee's mailbox. The investigation determined that personal information of 3 New Hampshire residents was affected. Notifications were sent on August 8, 2023, offering credit monitoring services. No evidence of misuse was found.
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.