whogothacked

Regence data breach record

Is there a breach on record for Regence?

Yes. There are five breach incidents on record for Regence. The most recent was first reported on May 21, 2026.

The most recent was reported to the HHS Office for Civil Rights.

The most recent incident

How many
2,856 individuals, per the HHS Office for Civil Rights.
Data listed
Not listed by the sources on record.
Source record
Open the HHS list of HIPAA breach reports at ocrportal.hhs.gov (how to find this record there)
What to do
If you received a notice letter, start with the letter: keep it, use any free monitoring it offers, and check that the letter is real.
Incidents on record
5
Newest incident first on record
Largest single figure
2,856 individuals per the HHS Office for Civil Rights

Jump to the incident first on record May 21, 2026, May 6, 2025, Jan 31, 2025, Apr 12, 2021 or Aug 16, 2019.

Get a daily email of new incidents

Email alerts

We use your address only for these alerts and to run and test the service (privacy). Want only SEC filings? Sign up on the alerts page.

Also filed as
Regence (Regence BS, Regence BSI and Regence BCBSO); Regence (Regence BlueShield and Regence BCBS of OR)
Sector
Health
State
Oregon

Was Regence hacked?

A source record describes a cyberattack. For the incident first reported on May 6, 2025, the record from the Washington Attorney General gives the cause as “Cyberattack: Phishing”.

Another record gives a cause in the source's own words. For the incident first reported on May 21, 2026, the record from the HHS Office for Civil Rights gives the cause as “Hacking/IT Incident (location of breached information: Network Server)”. For the incident first reported on April 12, 2021, the record from the HHS Office for Civil Rights gives the cause as “Hacking/IT Incident (location of breached information: Email)”.

The HHS Office for Civil Rights describes what happened in its own words. That description is quoted with the incident below.

A filing shows who notified the regulator. The filer is sometimes a vendor or a customer of the firm whose systems were affected, so a filing on its own does not establish whose systems were broken into.

The 5 incidents on record

First reported

Official record

1 source record

Regence reported a data breach to the US Department of Health and Human Services Office for Civil Rights in a notice filed on May 21, 2026. The HHS filing puts the number of individuals affected at 2,856. The HHS filing lists the type of breach as "Hacking/IT Incident (location of breached information: Network Server)".

Figures on record

  • 2,856individualsper the HHS Office for Civil Rights

This figure counts only the group named beside it.

Cause on record

Listed by HHS as “Hacking/IT Incident”.

The record behind this entry

  1. First record

    Listed on the HHS Office for Civil Rights breach portal under the name Regence.

    On this record: 2,856 individuals; cause given as “Hacking/IT Incident (location of breached information: Network Server)”.

    • Open the HHS list of HIPAA breach reports at ocrportal.hhs.govThe HHS breach portal has no page for each report. On its list, look for “Regence” (OR) with the breach submission date 05/21/2026. Look on its Under Investigation tab first; a report that has been resolved is on its Archive tab. Show Advanced Options can search the list by name (CE / BA Name Search) and by submission date.

What to do if this involved you

The sources on record do not list what kind of data was involved, so the notice letter is the place to look. What to do with a notice letter

First reported

Official record

1 source record

Regence reported a data breach to the Washington Attorney General in a notice filed on May 6, 2025. Breach dates in the filing run from November 5, 2024 to November 21, 2024. The Washington filing says the organization became aware of it on November 21, 2024. The Washington filing puts the number of Washington residents affected at 706. The Washington filing lists the cause as "Cyberattack: Phishing". The Washington filing lists the information involved as: names, social security numbers, driver's license or state id numbers, financial and banking information, dates of birth, health insurance policy or id numbers, medical information.

Breach dated
November 5, 2024 to November 21, 2024
Discovered
November 21, 2024

Figures on record

  • 706Washington residentsper the Washington Attorney General

This figure counts only the group named beside it.

Cause on record

Phishing.

Data exposed, as the sources list it

  • names
  • social security numbers
  • driver's license or state id numbers
  • financial and banking information
  • dates of birth
  • health insurance policy or id numbers
  • medical information

The record behind this entry

  1. First record

    Breach notice filed with the Washington Attorney General under the name Regence (Regence BS, Regence BSI and Regence BCBSO).

    On this record: 706 Washington residents; cause given as “Cyberattack: Phishing”; breach dated Nov 5, 2024 to Nov 21, 2024; discovered Nov 21, 2024; 7 kinds of data listed (shown above).

What to do if this involved you

  • Consider a credit freeze

    A freeze stops new credit being opened in your name. It is free, and you place it yourself with each of the three US credit bureaus: Equifax, Experian and TransUnion. You can check your credit reports for free as well.

    Free credit reports at AnnualCreditReport.com

  • Check your statements

    Look through recent card and bank statements for charges you do not recognize, and report any to your bank or card issuer. If your full card number was involved, ask for a replacement card.

  • Review medical and insurance statements

    Check statements from your insurer and providers for care you did not receive, and tell your insurer about anything that is not yours.

These steps follow from the kinds of data the sources list. If you have a notice letter, start with the letter.

First reported

Official record

1 source record

Regence reported a data breach to the Washington Attorney General in a notice filed on January 31, 2025. Breach dates in the filing run from December 5, 2024 to December 19, 2024. The Washington filing says the organization became aware of it on December 19, 2024. The Washington filing puts the number of Washington residents affected at 714. The Washington filing lists the cause as "Theft or Mistake". The Washington filing lists the information involved as: names, medical information.

Breach dated
December 5, 2024 to December 19, 2024
Discovered
December 19, 2024

Figures on record

  • 714Washington residentsper the Washington Attorney General

This figure counts only the group named beside it.

Data exposed, as the sources list it

  • names
  • medical information

The record behind this entry

  1. First record

    Breach notice filed with the Washington Attorney General under the name Regence (Regence BlueShield and Regence BCBS of OR).

    On this record: 714 Washington residents; cause given as “Theft or Mistake”; breach dated Dec 5, 2024 to Dec 19, 2024; discovered Dec 19, 2024; 2 kinds of data listed (shown above).

What to do if this involved you

  • Review medical and insurance statements

    Check statements from your insurer and providers for care you did not receive, and tell your insurer about anything that is not yours.

These steps follow from the kinds of data the sources list. If you have a notice letter, start with the letter.

First reported

Official record

1 source record

Regence reported a data breach to the US Department of Health and Human Services Office for Civil Rights in a notice filed on April 12, 2021. The HHS filing puts the number of individuals affected at 803. The HHS filing lists the type of breach as "Hacking/IT Incident (location of breached information: Email)".

Figures on record

  • 803individualsper the HHS Office for Civil Rights

This figure counts only the group named beside it.

Cause on record

Listed by HHS as “Hacking/IT Incident”. Happened at a vendor.

The record behind this entry

  1. First record

    Listed on the HHS Office for Civil Rights breach portal under the name Regence.

    On this record: 803 individuals; cause given as “Hacking/IT Incident (location of breached information: Email)”.

    In the words of the HHS Office for Civil Rights

    The covered entity (CE), Regence, reported that several employees of its business associate (BA) were the victims of an email phishing scheme that affected the protected health information (PHI) of 803 individuals. The PHI involved included names, addresses, dates of birth, Social Security numbers, drivers’ license numbers, financial and health insurance information, and treatment information. The BA notified HHS, affected individuals, the media, and provided complimentary credit monitoring services. In its mitigation efforts, the BA implemented additional administrative, technical, and security safeguards to better protect PHI.

    • Open the HHS list of HIPAA breach reports at ocrportal.hhs.govThe HHS breach portal has no page for each report. On its list, look for “Regence” (OR) with the breach submission date 04/12/2021. Reports older than 24 months are on its Archive tab. Show Advanced Options can search the list by name (CE / BA Name Search) and by submission date.

What to do if this involved you

This entry has no itemized list of the kinds of data involved. The description quoted above may name them, and a notice letter, if you received one, is the place to look. What to do with a notice letter

First reported

Official record

1 source record

Regence reported a data breach to the Washington Attorney General in a notice filed on August 16, 2019. The filing gives July 25, 2019 as the date of the breach. The Washington filing says the organization became aware of it on July 26, 2019. The Washington filing puts the number of Washington residents affected at 642. The Washington filing lists the cause as "Theft or Mistake". The Washington filing lists the information involved as: names, social security numbers.

Breach dated
July 25, 2019
Discovered
July 26, 2019

Figures on record

  • 642Washington residentsper the Washington Attorney General

This figure counts only the group named beside it.

Data exposed, as the sources list it

  • names
  • social security numbers

The record behind this entry

  1. First record

    Breach notice filed with the Washington Attorney General under the name Regence.

    On this record: 642 Washington residents; cause given as “Theft or Mistake”; breach dated Jul 25, 2019; discovered Jul 26, 2019; 2 kinds of data listed (shown above).

What to do if this involved you

  • Consider a credit freeze

    A freeze stops new credit being opened in your name. It is free, and you place it yourself with each of the three US credit bureaus: Equifax, Experian and TransUnion. You can check your credit reports for free as well.

    Free credit reports at AnnualCreditReport.com

These steps follow from the kinds of data the sources list. If you have a notice letter, start with the letter.

If you received a notice letter

  • Keep the letter

    It names the incident and lists which of your details were involved. The letter, not this page, is the authority on what happened to your data.

  • Use any free monitoring it offers

    Many notices include free credit monitoring with an enrollment code and a deadline. Enroll using the instructions printed in the letter, not a link from an email or text.

  • Check that the letter is real

    Compare it with the source records linked on this page. If you are unsure, contact the organization using a phone number or address from its own website, not one printed in a message you were sent.

  • If your identity is misused, report it

    The Federal Trade Commission's IdentityTheft.gov gives you a recovery plan and the forms to send.

    Report identity theft at IdentityTheft.gov

About this record

Official record: A regulator filing or the organization's own disclosure exists.

Being on record here is not a finding that Regence did anything wrong or broke any law. This page reports what the source records say, and no more.

Every fact on this page comes from the source records linked above. The steps for people who received a letter are general guidance, not part of the record. How records are verified

Something wrong here? See how to dispute an entry, or write to corrections@whogothacked.com.

The same record for software: /api/v1/orgs/regence