DataBreaches.Net

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

Is a third-party incident about to fuel a health insurance fraud ring?

Posted on April 4, 2019 by Dissent

Despite the fact that we are constantly bombarded with reports of breaches, there are even more breaches that seem to escape media coverage. I’ve been wondering about whether something I noticed recently might be something that will be used to fuel an insurance fraud operation.

My curiosity was triggered when I read a notification from Aetna. The insurer’s report described an incident at Availity, LLC, a clearinghouse.

According to Availity, it

operates the largest real time information network in healthcare, connecting over a million providers, health plans and their technology partners.

According to Aetna’s report, Availity had first notified them on November 10, 2018 that on November 2, they had discovered that some threat actor(s) had been authenticating as providers to fraudulently access information on insured members’ eligibility and benefits. On December 3, 2018, Availity reportedly provided Aetna with an update that indicated that the fraudulent activity had occurred  between May 25, 2017 and November 3, 2018.

By using the Availity portal, the unauthorized individuals would have been able to access names, addresses, dates of birth, name of primary care providers, health insurance member ID numbers, and information regarding health insurance eligibility and benefits. 

When it discovered what was happening, Availity terminated the fraudulent accounts, prohibited access to the portal by all users associated with the fraudulent accounts,  implemented additional security measures, and reported the matter to the FBI.

For its part, Aetna notified 114 of its members whose information had been accessed, but Aetna also informed this site last week that it is still investigating to see if more members need to be notified.

As of today, Availity’s provider registration portal is still under revision, it seems.

Availity’s provider registration portal is still being reviewed and secured five months after they detected misuse of their system.

After finding Aetna’s breach notification, and not getting any substantive answers from Availity, I  started searching.  I’ve since found a similar report filed in January by UnitedHealthcare, who reported  to the Maryland Attorney General’s office that Availity had informed them that 41 of their Maryland members’ information had been accessed between July 7, 2017 and March 27, 2018 by fraudulently created provider accounts.  The number of non-Maryland members who may also have been affected was not disclosed.

I also found a similar notification from a third insurer, Humana. They reported that they were told that on February 14, 2019, Availity had first discovered suspicious activity affecting their members, and that investigation subsequently revealed that improper access had occurred between January 15, 2016 and February 21, 2018.  The number of affected Humana members was not disclosed.

It’s clear from the three insurers’ reports that criminal activity may have been occurring for years but had gone undetected until later in 2018. But how many more insurers had members’ information accessed by the attackers?  DataBreaches.net does not know with certainty because Availity would not answer questions, claiming that they couldn’t answer questions about a situation that’s a law enforcement investigation, but a source with knowledge of the investigation informed DataBreaches.net that they believe Availity notified 22 insurers whose members’s information had been accessed by the attackers.

The only helpful detail Availity provided  was:

While the investigation is still ongoing, it appears that the fraudulent users conducted non-financial transactions on the portal using certain personal information they already possessed. We have no reason to believe this information was obtained from Availity.

So all I have in hand are three reports from insurers, and a source who says that 22 insurers were notified. But here are a few  questions to think about:

Was the Availity attack related to an incident last year where attackers  authenticated as insurance agents or brokers to acquire personal information on  75,000 individuals seeking health insurance on Healthcare.gov? (Make that 93,600).

What happened to these people’s information and to the information acquired in the Availity incident?  Has it shown up anywhere for sale? Is it being used for insurance fraud? Is it being hoarded for future use? 

Maybe it’s time for us all to be more concerned than relieved when a breached entity tells us that there’s no evidence that our stolen ePHI has been misused. Rather than breathing a sigh of relief, maybe we should be wondering what it’s being saved for.

No related posts.

Category: Breach IncidentsCommentaries and AnalysesHackOf Note

Post navigation

← Health data breaches due to external actors continue to predominate recently.
Sensitive data from 8,000 people exposed in privacy breach at BC Pension Corporation after microfiche goes missing during office move. →

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

  • India’s Max Financial says hacker accessed customer data from its insurance unit
  • Brazil’s central bank service provider hacked, $140M stolen
  • Iranian and Pro-Regime Cyberattacks Against Americans (2011-Present)
  • Nigerian National Pleads Guilty to International Fraud Scheme that Defrauded Elderly U.S. Victims
  • Nova Scotia Power Data Breach Exposed Information of 280,000 Customers
  • No need to hack when it’s leaking: Brandt Kettwick Defense edition
  • SK Telecom to be fined for late data breach report, ordered to waive cancellation fees, criminal investigation into them launched
  • Louis Vuitton Korea suffers cyberattack as customer data leaked
  • Hunters International to provide free decryptors for all victims as they shut down (2)
  • SEC and SolarWinds Seek Settlement in Securities Fraud Case

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

  • German court awards Facebook user €5,000 for data protection violations
  • Record-Breaking $1.55M CCPA Settlement Against Health Information Website Publisher
  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t
  • Oregon Amends Its Comprehensive Privacy Statute

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.