DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Oregon workers’ compensation claimants and policyholders may have had their personal information hacked

Posted on January 9, 2023 by Dissent

Mike Rogoway reports that Oregon’s worker’s compensation insurer, SAIF Corp., experienced a breach in October that potentially compromised policyholders’ information and workers’ compensation claimants’ personal and medical information.

On their breach-related site maintained for them by IDX, SAIF explains that on October 24, there was a brief period during which an unauthorized individual or individuals were able to access and acquire files from their network. They write:

Following an analysis of that data by third-party cybersecurity experts, we have evidence to suggest that the majority of the accessed data was from information collected prior to 2003. If you had a policy or a claim before January 1, 2003, there is a possibility that your data was compromised. For policyholders, that data may have included Social Security numbers, financial account numbers, and medical information about employees of policyholders. For claimants, the data may have included Social Security numbers, driver’s license numbers, financial account numbers, health insurance policy numbers, and medical history information.

They offer no statement as to why they were still storing files from prior to 2003, but a spokesperson for SAIF sent DataBreaches the following statement in response to our question about whether retention was required:

SAIF is subject to ORS 192 requiring records retention and our specific record retention schedule is approved by the Oregon State Archivist. SAIF is required to retain policy files and worker accident claim files for 75 years from the date of the policy or, in the case of a claim, the worker’s injury.

DataBreaches also inquired whether the old files had been connected to the internet without any encryption. The spokesperson responded:

We moved to all electronic files and, as part of this, scanned older paper files. The files were not encrypted but stored on an internal system not exposed to the internet through any of SAIF’s customer facing systems.

SAIF’s statement also states:

There is also evidence a limited amount of recent claimant data may have been impacted. If you are a claimant and received any written communication from SAIF on your claim dated between September 24, 2022, and October 25, 2022, there is a possibility that data was also compromised. This data was limited to the accepted and denied medical conditions in the claim.

According to Rogoway, SAIF notified customers on Dec. 8.  The number of people possibly affected has not been disclosed at this point.

In response to another queston from DataBreaches about whether SAIF has received any ransom message or communication, the spokesperson responded that SAIF did not receive a ransom message.

 

 

 

Category: Breach IncidentsHackMiscellaneousU.S.

Post navigation

← What Twitter’s 200 million email leak really means
When ransom negotiations become public, self-inflicted reputation harm may follow →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Department of Justice says Berkeley Research Group data breach may have exposed information on diocesan sex abuse survivors
  • Masimo Manufacturing Facilities Hit by Cyberattack
  • Education giant Pearson hit by cyberattack exposing customer data
  • Star Health hacker claims sending bullets, threats to top executives: Reports
  • Nova Scotia Power hit by cyberattack, critical infrastructure targeted, no outages reported
  • Georgia hospital defeats data-tracking lawsuit
  • 60K BTC Wallets Tied to LockBit Ransomware Gang Leaked
  • UK: Legal Aid Agency hit by cyber security incident
  • Public notice for individuals affected by an information security breach in the Social Services, Health Care and Rescue Services Division of Helsinki
  • PowerSchool paid a hacker’s extortion demand, but now school district clients are being extorted anyway (3)

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Clothing Retailer, Todd Snyder, Inc., Settles CPPA Allegations Regarding California Consumer Privacy Act Violations
  • US Customs and Border Protection Plans to Photograph Everyone Exiting the US by Car
  • Google agrees to pay Texas $1.4 billion data privacy settlement
  • The App Store Freedom Act Compromises User Privacy To Punish Big Tech
  • Florida bill requiring encryption backdoors for social media accounts has failed
  • Apple Siri Eavesdropping Payout Deadline Confirmed—How To Make A Claim
  • Privacy matters to Canadians – Privacy Commissioner of Canada marks Privacy Awareness Week with release of latest survey results

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.