Washington State AG
Clustered 9 filings across 8 jurisdictions · filing window Mar 14, 2025 → Jul 1, 2025. View entity profile → Other incidents for this victim →
incident inc_0d04e511df9f4ed4 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Financial account
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
CA MD ME MT NH OR TX WA
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
9 filings across 8 jurisdictions · Mar 14, 2025 – Jul 1, 2025 · 3 milestones
Oct 12, 2024 → Oct 24, 2024
When the intrusion reportedly occurred, per the linked filings
Jan 27, 2025
Reported by CALIFORNIA AG, MARYLAND AG, MAINE AG, NEW HAMPSHIRE AG, WASHINGTON AG filings
Jun 3, 2025
Reported by TEXAS AG filing
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.
Western Alliance Bank disclosed a data breach involving a third-party vendor's secure file transfer software. An unauthorized actor exploited an unknown vulnerability in the software to access Western Alliance's systems between October 12 and October 24, 2024, and exfiltrated files. The bank discovered the incident on January 27, 2025. Affected data includes names, Social Security numbers, and potentially financial account numbers, driver's license numbers, and tax identification numbers. The bank is offering one year of complimentary credit monitoring.
Western Alliance Bank notified the Maryland AG of a data security incident affecting 11 Maryland residents. A threat actor exploited an unknown vulnerability in a third-party secure file transfer software between Oct 12-24, 2024, to access files containing names, SSNs, DOBs, financial account numbers, driver's licenses, and passports. WAB engaged forensic investigators, notified law enforcement, and is offering credit monitoring.
Affected (this filing): 11
Western Alliance Bank reported a data breach to the Montana Attorney General. The breach was reported on 2025-03-14. The breach occurred on 01/27/2025. 35 Montana residents were affected.
Affected (this filing): 35
Western Alliance Bank reported a data breach affecting 6 Maine residents. The breach, described as an external system breach (hacking), occurred between October 12 and October 24, 2024, and was discovered on January 27, 2025. Affected individuals were notified on March 14, 2025, and offered 12 months of identity theft protection services through Experian.
Affected (this filing): 6
Western Alliance Bank notified the New Hampshire Attorney General on March 14, 2025, of a data security incident involving the personal information of two NH residents. A threat actor exploited an unknown vulnerability in a third-party secure file transfer software used by the bank to access files between October 12-24, 2024. The bank detected the unauthorized access on January 27, 2025, engaged forensic investigators, notified law enforcement, and is offering credit monitoring to affected individuals.
Affected (this filing): 2
Western Alliance Bank ("WAB"), a finance sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-01-27 and filed notice on 2025-06-30. 539 Washington residents were affected. 154 days elapsed between awareness and notification. 107 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 539
Western Alliance Bank ("WAB") reported a data breach to the Oregon Attorney General. The breach was reported on 2025-06-30. The breach occurred during 10/12/2024 - 10/24/2024. The breach was discovered on 1/27/20256/3/2025. 78,338 individuals were affected. Notice was sent on 3/14/20256/30/2025.
Affected (this filing): 78,338
Western Alliance Bank filed a supplemental notice with the New Hampshire Attorney General regarding a data security incident involving a third-party secure file transfer software. Unauthorized access occurred between October 12-24, 2024. The bank discovered the incident on January 27, 2025. A comprehensive review determined that personal information (including SSN, tax ID, driver's license, and financial account data) of 39 additional New Hampshire residents was compromised. Notifications were mailed on June 30, 2025, offering credit monitoring services.
Affected (this filing): 39
Western Alliance Bank ("WAB") based in Phoenix, Arizona, a financial services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-06-03 and reported on 2025-07-01. 1,222 Texas residents were affected. 78,338 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Date of Birth. Consumers were notified via U.S. Mail.
Affected (this filing): 1,222