Yuma Regional Medical Center notifying approximately 700,000 patients of ransomware attack
Yuma Regional Medical Center (YRMC) said it mailed letters to thousands of patients whose information may have been involved in a recent cybersecurity incident.
On April 25, 2022, YRMC identified a ransomware incident affecting some internal systems. Upon detecting the incident, YRMC shared with News 11 it took immediate action, taking systems offline, and communicating with law enforcement.
An investigation was launched with the help of a third-party forensic firm. YRMC said the investigation determined that an unauthorized person gained access to YRMC’s network between April 21 and April 25 and removed a subset of files from YRMC’s systems during that time.
Read more at KYMA
There is only a brief statement on YRMC’s website at this time:
Yuma Regional Medical Center recently experienced a ransomware incident that is impacting some of our operations. We are working closely with law enforcement and our third-party cybersecurity experts to investigate this incident and bring our systems back online as quickly and safely as possible, in a way that prioritizes patient care.
Nothing is more important to us at YRMC than the health and safety of our patients. Our facilities remain open, and we continue to provide care for our patients using established back-up processes and other downtime procedures. Nevertheless, we understand there are certain delays in our services, and we recognize this is an inconvenience. At this time, most appointments continue to take place as scheduled. If for any reason an appointment needs to be rescheduled, we will contact that patient directly. For inquiries regarding appointments, scheduling, or patient care, please contact your provider’s office and a team member will get back to you.
We are grateful for the cooperation and support of our employees, patients, families, and community partners while we continue to work through this incident, and we will share additional information as appropriate.
As of the time of this publication, no threat actor group has publicly claimed responsibility for this attack.