DataBreaches.Net

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

NY: Four Winds Hospital reveals September ransomware attack

Posted on November 23, 2020 by Dissent

On September 1, Four Winds Hospital in Katonah, New York discovered that they had been attacked. On November 14, they issued a statement on their site and in local media. From that statement:

What happened?  In September 2020, Four Winds Hospital in Katonah was the victim of a ransomware attack that prevented the Hospital from accessing its computer systems.  We learned of the attack on September 1st and we were not able to access our computer networks for two weeks.

How did the Hospital secure patient data?  We immediately notified NYS and federal law enforcement agencies which began an investigation of the incident and the cybercriminals behind it.   We quickly locked-out the cybercriminals from continuing to access our systems.   We also engaged cybersecurity experts to assist us in responding to the attack and help us to determine what, if any, patient data was impacted. They obtained evidence that the cybercriminals deleted any files in their possession, although that evidence cannot be independently verified.  The Hospital has taken steps to prevent a reoccurrence.

They obtained “evidence that the cybercriminals deleted any files in their possession?” That suggests that the hospital paid ransom, although they do not say that they did. In any event, any “evidence” of data destruction cannot be relied upon, of course.

What information was involved?  Our forensic investigation determined that encrypted data fields, email, and any information in cloud based and encrypted programs were NOT accessed by the cybercriminals.  The patient electronic medical record system was NOT accessed.   The cybercriminals were able to access password protected data files.  We then conducted a file-by-file search to determine whether those files contained any personal patient information.  That search revealed that some files that could have been accessed during the time the cybercriminals retained possession of them included: lists of patients from 1983 to the present by name and medical record number; a small subset of patient lists (approximately 100 records) that also contained a patient’s social security number; some files dating back to 2013 that contained miscellaneous documents that included limited patient treatment information; and the social security number of patients who were Medicare members admitted earlier than 2019 during the time that Medicare cards displayed that number.

You can read the full statement on their site, but once again, why was so much old data available? All of those patients need to be contacted whereas moving old files like that offline likely would have saved the hospital a lot of time and money.

There is no entry on HHS’s public breach tool for this incident — at least not yet.


Related:

  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Confidence in ransomware recovery is high but actual success rates remain low
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • KT Chief to Resign After Cybersecurity Breach Resolution
Category: Breach IncidentsHealth DataMalwareU.S.

Post navigation

← Pays de la Loire: Ouest-France victim of a cyberattack
Over 300K Spotify accounts hacked in credential stuffing attack →

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

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

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

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.