DataBreaches.Net

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

Malware incident discovered in May, 2017 affected 2,600 patients: Partners HealthCare System

Posted on February 5, 2018 by Dissent

Partners HealthCare System, whose hospitals include Massachusetts General and Brigham and Women’s, revealed today that it had discovered a malware attack in May, 2017 that may have exposed 2,600 patients’ information. They learned of the problem on May 8, but because data was mixed in with code, numbers, other data, and unformatted, it took them quite a while to figure out who was impacted and who needed to be notified.

The statement on their web site begins:

On May 8, 2017, Partners HealthCare System, Inc. (“Partners”) became aware that our computer network had been affected by a sophisticated, malicious computer program introduced by an unauthorized third party.  Our monitoring systems identified suspicious activity, and we immediately blocked some of this malware and began an investigation working with third party forensic consultants to identify the problem and mitigate its impact.

We were able to determine that the malware was not specifically targeted to impact the Partners environment, Partners operations or any information maintained by Partners.  We also confirmed that there was no access to our electronic medical record system.  As we continued the investigation, however, we became aware that the malware may have resulted in unauthorized access to certain data resulting from user activity on affected computers from May 8, 2017 to May 17, 2017.  As impacted computers were identified, Partners implemented aggressive containment measures to mitigate further impact.

As part of our ongoing review, we became aware on July 11, 2017 of data that appeared to possibly involve personal and health information.  The impacted data was not in any specific format, and it was mixed in together with computer code, dates, numbers and other data, making it very difficult to read or decipher.  After an extensive manual data analysis completed in December 2017, we are notifying individuals whose personal and health information may have been involved, in an abundance of caution.  Based on the review, the information involved may have included certain types of protected health information for patients, including first and last name, date(s) of service, and/or certain limited amounts of clinical information such as procedure type, diagnosis, and/or medication. For some patients, Social Security Numbers and financial account data may have been involved.   However, we are currently not aware of any misuse of patients’ health information.  

Read more of their statement on their site.

h/t  Boston Business Journal


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
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
Category: Health DataMalwareU.S.

Post navigation

← 12 UNC employees’ personal information comprised in cybersecurity breach
Man sues T-Mobile for allegedly failing to stop hackers from draining his cryptocurrency account →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • 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

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • 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

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.