Trubee Wealth Advisors reported a data breach to the Montana Attorney General. The breach was reported on 2025-09-26. The breach occurred on 08/14/2025. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filing window Sep 26, 2025 → Dec 24, 2025. View entity profile → Other incidents for this victim →
incident inc_731b56f12e5b4e54 · merge_method human · confidence 100%
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
MT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 14, 2025
When the intrusion reportedly occurred, per the linked filings
Trubee Wealth Advisors reported a data breach to the Montana Attorney General. The breach was reported on 2025-09-26. The breach occurred on 08/14/2025. 2 Montana residents were affected.
Affected (this filing): 2
Trubee Wealth Advisors offers a diverse range of investment servi ces tailored for individuals, small businesses, corporations, and philanthropic organizations. We will upload 165gb of corporate data soon. Clients and employee s information (passports, driver licenses, birth and death certs, w9 forms), accounting, financial statements, benefits, financial analysis, capital and profit, clearing contract analysis, verifi cation of funds letter, compliance, licensing, HR information, ou tside brokerage, client DB, confidential client information, NDA and so on.
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.