Waller Lansden Dortch & Davis LLP reported a data breach to the Montana Attorney General. The breach was reported on 2022-03-16. The breach occurred from 11/15/2021 to 11/25/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Mar 16, 2022. View entity profile → Other incidents for this victim →
incident inc_72211a973dc94ae7 · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 15, 2021
When the intrusion reportedly occurred, per the linked filings
Nov 25, 2021
Reported by MAINE AG filing
Waller Lansden Dortch & Davis LLP reported a data breach to the Montana Attorney General. The breach was reported on 2022-03-16. The breach occurred from 11/15/2021 to 11/25/2021. 1 Montana residents were affected.
Affected (this filing): 1
Waller Lansden Dortch & Davis LLP, a law firm, experienced a ransomware incident on November 18, 2021, which was discovered a week later on November 25, 2021. The breach impacted 2,522 individuals, compromising their names and financial account or credit/debit card numbers along with associated access codes. The firm notified affected individuals on March 16, 2022, and offered one year of identity protection services through Kroll.
Affected (this filing): 2,522
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.