NL: Data leak at Radboudumc hospital was caused by former employee

This is a Google translation of a story in Dutch:

The data breach at Radboudumc in Nijmegen is due to a former employee, the hospital reports in an update . Due to the leak, the data of an unknown number of employees is on the street.

The hospital discovered the data breach earlier this month. Names, login names, email addresses and phone numbers of hospital employees have been leaked. The data of employees of organizations with which Radboudumc collaborates are also on the street.

The hospital now reports that a former employee has put files online on GitHub, an online platform where software developers share knowledge with each other. It mainly concerned scripts, codes that are used to automate processes. However, it also contained confidential information, such as personal data.

Read more on nu.nl

DataBreaches.net asked researcher Jelle Ursem to comment on this incident. Ursem has been discovering and reporting on data leaks on GitHub for years now, including findings we jointly published in a 2020 paper, No Need to Hack When It’s Leaking and in a 2021 post, Good Luck Explaining to HHS Why Your PHI is in GitHub’s Vault for the Next 1,000 Years.

Ursem comments on today’s news:

This once again draws attention to how important it is to train any new employees and make sure they understand it’s NOT okay to use Github or any other third party file storage to take your employer’s work home or even temporarily store it. In my initial research from 2 years ago, I compiled a list of all the host names for Dutch hospitals and ran them through the search and back then there were no hits, thankfully. There has been more than enough press coverage about ransomware attacks and password leaks in the last couple of years. I cannot wrap my mind around how anyone can still make this mistake.

To any developers out there reading this: Do yourself a favor, check up on your assets regularly by typing “Yourcompanyname” into the Github search box, and verify that what you see should actually be public.

And please….
Stop Uploading Passwords To Github.

About the author: Dissent

Comments are closed.