DataBreaches.Net

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

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

Posted on August 25, 2021 by Dissent

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.


Related:

  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • Romanian prisoner hacks prison IT system in plot made for a Netflix movie
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • UK: 'Catastrophic' attack as Russians hack files on EIGHT MoD bases and post them on the dark web
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • Heritage Provider Network $49.99M Class Action Settlement
Category: ExposureHealth DataNon-U.S.

Post navigation

← Alibaba Cloud data leak ‘violated Cybersecurity Law’ in 2019 and must rectify, local Chinese telecoms regulator says
Educational institution ROC Mondriaan in The Hague victim of major cyber 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

  • 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.