DataBreaches.Net

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

Confidential medical records from Bronx-Lebanon Hospital exposed online by vendor’s error

Posted on May 9, 2017 by Dissent

Vendor’s error appears to have exposed personal and confidential medical data of patients seen at Bronx-Lebanon Hospital Center since 2014;
Records also include addiction histories, psych histories, and histories of physical or sexual abuse;
Hospital investigating to determine what happened and who may have accessed data.

By now, you may be tired of reading reports on misconfigured MongoDB installations or rsync backups.  If it’s any consolation, I’m tired of reporting on all these leaky and/or misconfigured installations, but … they’re still happening. It’s almost as if no one is listening to any of the researchers begging entities to  secure their data. How many MongoDB servers have to be totally wiped out or ransomed before more people start checking whether they left port 27017 open? How many more nude photos of patients or ultrasound images will be exposed because of misconfigured Rsync backups? And of course, if the government hadn’t thrown researcher Justin Shafer in jail on cyberstalking charges, he’d probably still be uncovering firms and covered entities that expose what should be protected health information on public FTP servers.

But as concerning as the PII leaks of patient data are, the ones with sensitive protected health information are even more concerning to this blogger.

iHealth Innovations

On May 3, Bob Diachenko of  the Kromtech (MacKeeper) Security Research Center contacted me after finding what appeared to them to be tens of thousands or even millions of patients’ records exposed due to yet another misconfigured rsync backup.  At Bob’s request, after reviewing some of the data he sent me, I agreed to assist him with trying to make notifications. Inspection of the data had suggested that the backup was managed by iHealth Innovations, but that the patient records were from Bronx-Lebanon Hospital Center in New York City. 

Bronx-Lebanon Hospital

Unable to reach anyone at iHealth Innovations other than their switchboard, with whom I left a message, I attempted to notify the hospital, while Kromtech also attempted to make notifications. I cannot say that notification to the hospital was quick or easy, but within an hour or so, the data were secured, and by the next day, I had received three call-backs from the hospital and the vendor. Both thanked me for alerting them to the problem and promised to get back to me with some explanation or answers to my questions.

Neither followed up as promised, however.  A hospital spokesperson did return my call yesterday, and asked me what my questions were. Then he didn’t answer any of them, telling me only that they were investigating and would have no further comment at this time. The hospital wouldn’t even answer a basic question such as “Why does iHealth Innovations have all this patient data? What does iHealth do for the hospital?” Neither did iHealth Innovations follow up despite their assurances.

So no, we didn’t get to the question of whether any business associate agreement was in place and how the hospital evaluated their vendor’s data security or whether the vendor even needed all that personal and confidential medical information to do its job for the hospital. The data that Kromtech sent me appeared to be from 2014 and 2015 but a listing of the directories and folders indicates that the exposed backup also contained records from 2016 and 2017.

As noted previously, the records contained a lot of sensitive medical information in addition to personally identifiable information such as name, address, telephone number, date of birth, Social Security number, etc. Here are two redacted snippets, below. The lines giving the patients’ names and other details have been cropped and other details are redacted. Some may be shocked by the amount of detail in the records, which is precisely why I am posting redacted snippets: imagine if these records were yours or a family member’s. Do you really want all these hospital records exposed on the internet because of a vendor’s error? Do you even want a vendor to have all this sensitive information?

Sensitive information on identifiable patients was exposed due to a misconfigured backup device. Image redacted by DataBreaches.net.
Sensitive information on identifiable patients was exposed due to a misconfigured backup device. Image redacted by DataBreaches.net.

The preceding redacted snippets are from files in the Addiction unit. According to what Diachenko found via a Shodan search, and you can read his report here, records and files from a number of departments were publicly accessible and viewable, including cardiology, surgery, pulmonology, psychiatry, and neurosurgery.

At the present time, DataBreaches.net does not know if anyone other than Kromtech’s research team accessed these medical records and other personal data. Nor does DataBreaches.net have a clear sense as to many unique patients’ records were involved, although Diachenko indicates it could be tens of thousands to millions. Whether the hospital or vendor will notify HHS or any regulators or patients remains to be seen.

This post will be updated if or when the hospital or vendor provide additional information.


Related:

  • Two more entities have folded after ransomware attacks
  • British institutions to be banned from paying ransoms to Russian hackers
  • Data breach feared after cyberattack on AMEOS hospitals in Germany
  • Microsoft Releases Urgent Patch for SharePoint RCE Flaw Exploited in Ongoing Cyber Attacks
  • Global hack on Microsoft product hits U.S., state agencies, researchers say
  • Inquiry launched after identities of SAS soldiers leaked in fresh data breach
Category: Breach IncidentsExposureHealth DataOf NoteU.S.

Post navigation

← Website Flaw Let True Health Diagnostics Users View All Medical Records
Funding Circle Error Exposes 6,000 SSNs Of American Clients →

4 thoughts on “Confidential medical records from Bronx-Lebanon Hospital exposed online by vendor’s error”

  1. Regret says:
    May 9, 2017 at 1:17 pm

    You’re right, the amount of detail is horrifying. I’m guessing they won’t talk to you because they are busy hiring lawyers and PR experts who will issue the standard announcement: “Information technology policies were not adhered to… remedial action will be taken… updating security policies… offering subscription to a credit monitoring service.”

  2. Nikki Jam says:
    May 13, 2017 at 11:45 am

    As of 5/13/2017, Bronx Lebanon hospital (Bronx NY) was hit with another cyber attack and our whole system was affected and still is affected.

    1. Dissent says:
      May 13, 2017 at 3:40 pm

      Are you referring to the Wanna Cry ransomware attack?

  3. Xio Felix says:
    May 13, 2017 at 11:51 am

    Bronx Lebanon was hit and so was lots of other hospitals

Comments are closed.

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

  • BlackSuit ransomware site seized as part of Operation Checkmate
  • The day after XSS.is forum was seized, it struggles to come back online — but is it really them?
  • U.S. nuclear and health agencies hit in Microsoft SharePoint breach
  • Russia suspected of hacking Dutch prosecution service systems
  • Korea imposes 343 million won penalty on HAESUNG DS for data breach of 70,000 shareholders
  • Paying cyberattackers is wrong, right? Should Taos County’s incident be an exception? (1)
  • HHS OCR Settles HIPAA Ransomware Investigation with Syracuse ASC for $250k plus corrective action plan
  • IVF provider Genea notifies patients about the cyberattack earlier this year.
  • Key figure behind major Russian-speaking cybercrime forum targeted in Ukraine
  • Clorox Files $380M Suit Alleging Cognizant Gave Hackers Passwords in Catastrophic 2023 Cyberattack

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

  • Indonesia asked to reassess data privacy terms in new U.S. trade deal
  • Meta Denies Tracking Menstrual Data in Flo Health Privacy Trial
  • Wikipedia seeks to shield contributors from UK law targeting online anonymity
  • British government reportedlu set to back down on secret iCloud backdoor after US pressure
  • Idaho agrees not to prosecute doctors for out-of-state abortion referrals
  • As companies race to add AI, terms of service changes are going to freak a lot of people out. Think twice before granting consent!
  • Uganda orders Google to register as a data-controller within 30 days after landmark privacy ruling

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.