Willis Towers Watson US LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-04. The breach occurred from 5/29/2023 to 5/30/2023. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Aug 4, 2023 → Aug 8, 2023. View entity profile → Other incidents for this victim →
incident inc_7243738678ed463f · 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
May 29, 2023
When the intrusion reportedly occurred, per the linked filings
Jun 22, 2023
Reported by MAINE AG filing
Willis Towers Watson US LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-04. The breach occurred from 5/29/2023 to 5/30/2023. 1 Montana residents were affected.
Affected (this filing): 1
Willis Towers Watson US LLC and its affiliate Acclaris, Inc. reported a data breach affecting 4 Maine residents. The breach originated with a third-party vendor, Pension Benefit Information, LLC (PBI), which uses the MOVEit Transfer software. A zero-day vulnerability in MOVEit was exploited by a threat actor between May 29 and May 30, 2023, leading to data exfiltration. The compromised information includes names and Social Security numbers. The breach was discovered on June 22, 2023, and affected individuals were notified on August 10, 2023, with an offer of 24 months of identity monitoring services from Kroll.
Affected (this filing): 4
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.