Where does the Western Alliance Bank (WAB) case file come from?

Every entry is taken from the breach report Western Alliance Bank (WAB) lodged with the Oregon Attorney General. Nothing here is estimated.

Why do the incident date and the report date differ?

Companies usually investigate before they report. The gap between the two dates shows how long that took.

What does the records-affected figure count?

It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.

Does this case file change over time?

Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

Case file

Case File: Western Alliance Bank (WAB) Data Breach

This file collects the dated facts on record for the Western Alliance Bank (WAB) incident. The state report is dated June 30, 2025. The incident itself is dated October 12, 2024.

Timeline

261 days separate the incident date from the date it was reported.

October 12, 2024Incident dateWhen the filing says the breach took place.
June 30, 2025Report filed in OregonDate the notice was lodged with the Oregon Attorney General.

Case facts

Filing state: Oregon
Date reported: June 30, 2025
Incident date: October 12, 2024
Receiving office: Oregon Attorney General

Case notes

Western Alliance Bank (WAB) has reported a data security incident to regulators, with the filing date noted as June 30, 2025. The breach itself was identified as occurring on October 12, 2024. The filing indicates an ongoing investigation into the specifics of the event, and the type of breach has not been disclosed.

While the exact categories of exposed personal information have not been specified in the public record, it is understood that data belonging to individuals was involved. The filing does not indicate how many people may have been affected by this incident.

Because the investigation is still active, Western Alliance Bank has not yet provided full details regarding the scope or impact of the breach. This information comes from public filings made with regulatory bodies.

Individuals who receive a direct notification from Western Alliance Bank regarding this incident should carefully review it for specific details pertaining to their situation. It is always wise to remain vigilant for any unusual activity involving your personal accounts and credit.

Consider implementing general security best practices. This includes monitoring financial statements and credit reports for unauthorized activity, changing passwords for online accounts, and being cautious of unsolicited communications that may attempt to phish for more information. Placing a fraud alert or security freeze on your credit file can also offer protection against identity theft.

Questions about this case file

Where does the Western Alliance Bank (WAB) case file come from?: Every entry is taken from the breach report Western Alliance Bank (WAB) lodged with the Oregon Attorney General. Nothing here is estimated.
Why do the incident date and the report date differ?: Companies usually investigate before they report. The gap between the two dates shows how long that took.
What does the records-affected figure count?: It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.
Does this case file change over time?: Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

Oregon data breaches

Filing source: Oregon Attorney General

Named in the Western Alliance Bank (WAB) breach?

Attach your notice and a short note. An attorney checks it against this case file at no cost.

Timeline

Case facts

Case notes

Questions about this case file

More Oregon case files