DataBreaches.Net

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

No Need to Hack When It’s Leaking.. and Leaking… and Leaking…

Posted on July 18, 2023 by Dissent

Today’s “No Need to Hack When It’s Leaking” episode is actually an update on a leak where DataBreaches did not name the entity at the time because the leak had not been secured.  It still hasn’t been secured. Now the entity is reportedly attempting to tell the U.S. Department of Health & Human Services that they were never contacted by any of the entities that had contacted them, that it’s not their bucket, and that someone else must own that bucket. Grab your favorite beverage and read on…

In 2022, DataBreaches filed a watchdog complaint with HHS about a leak of patient information. The patient data appeared to be from a Florida nursing services entity and was exposed in an unsecured Amazon bucket. Attempts by multiple entities to alert the Florida firm to the leak were unsuccessful, as outlined in our previous post.

This week, I learned that the entity was telling HHS investigators that they had never been contacted by any of the entities I named in my complaint and that it wasn’t their bucket and maybe I had the wrong entity.

HHS asked me if I could send them evidence to support my claims.

So I started searching thru my files and contacted Jelle Ursem, one of the researchers who had reported discovering that leak and who had called the entity twice trying to disclose responsibly, to no avail.  I also contacted Blue Cross Blue Shield and asked if they had logged their phone call to the entity.

Ursem had called the entity and had a phone log of the call to the phone number listed on the entity’s website.

I  had a copy of the email I had sent the entity and a copy of the draft report that Ursem had prepared for them and that they would have received if they had ever called him back.

Blue Cross Blue Shield’s intel team had a phone log that showed the date, timestamp and phone number they had called. And they remembered the call because the woman asked them who they were and when they told her, she said thank you and just hung up.

As of today, the bucket is STILL unsecured. And in that bucket are oh-so-many files with the entity’s name, address, and telephone number — the same telephone number that we all called and the same domain that DataBreaches had emailed.

If the bucket is not theirs, it’s likely a vendor’s, as I pointed out to them in my original email of December 2022, but it’s still their patient data and responsibility.

HHS has plenty of evidence linking the files in the bucket and the bucket itself to this entity. I told the investigator that I was not withdrawing my complaint and someone had a lot of explaining to do to them.

I hope HHS doesn’t give them a pass on this one. Not after so many people tried to alert them and a bucket with protected health information has been exposed for 4 years.


Related:

  • Missouri Adopts New Data Breach Notice Law
  • Qantas obtains injunction to prevent hacked data’s release
  • Ransomware attack disrupts Korea's largest guarantee insurer
  • Theft from Glasgow’s Queen Elizabeth University Hospital sparks probe
  • Global operation targets NoName057(16) pro-Russian cybercrime network in Operation Eastwood
  • More than 100 British government personnel exposed by Ministry of Defence data leak
Category: ExposureHealth DataU.S.

Post navigation

← Phoenician Medical Center notifying 162,500 patients of attack that “disrupted” IT systems
Announce: New category on DataBreaches.net →

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

  • 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
  • UK sanctions Russian cyber spies accused of facilitating murders
  • Michigan ‘ATM jackpotting’: Florida men allegedly forced machines to dispense $107K
  • Premier Health Partners issues a press release about a breach two years ago. Why was this needed now?
  • Bitcoin holds steady as hackers drain over $40 million from CoinCDX, India’s top exchange
  • Government will ‘robustly defend’ compensation claims from Afghans put at risk by data breach
  • Authorities released free decryptor for Phobos and 8base ransomware
  • Singapore Facing ‘Serious’ Cyberattack by Espionage Group With Alleged China Ties

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

  • 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
  • Meta investors, Zuckerberg reach settlement to end $8 billion trial over Facebook privacy violations
  • ICE is gaining access to trove of Medicaid records, adding new peril for immigrants
  • Microsoft can’t protect French data from US government access

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.