DataBreaches.Net

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

Aetna first notifying 238 Virginia employees of BenefitMall breach that they’ve known about since December, 2018?

Posted on June 5, 2019 by Dissent

In January, 2019, we learned about a breach at Centerstone Insurance and Financial Services, Inc. d/b/a BenefitMall, a business associate.  The breach reportedly affected more than 111,000 insurance members/covered employees of the vendor’s clients. HIPAA Journal covered the incident.

Yesterday, Aetna issued a public notice  related to the incident. Surprisingly, their notice discloses that by December 18, 2018, they had received information from BenefitMall as to which employees were potentially impacted.

So why did it take Aetna from then until this week to handle notifications for a few hundred people in Virginia?  That seems way too long a gap.

Public Notice
AETNA NOTIFIES MEMBERS OF VENDOR PRIVACY BREACHThis serves as a public notice that Aetna, a CVS Health business (NYSE: CVS), has notified approximately [238] [Virginia ] residents that Centerstone Insurance and Financial Services, Inc. d/b/a BenefitMall, a general agent that also acts as a third-party vendor that Aetna utilizes to provide administrative services related to employee benefits (e.g., enrollment and billing services), had certain employee email accounts compromised. Aetna confirmed that this incident did not involve any Aetna system or application, and did not involve any personal information that Aetna maintained.BenefitMall notified Aetna on December 11, 2018 that Aetna members may have been impacted by the breach. On December 18, 2018, BenefitMall provided Aetna with a list of potentially affected members. Upon receipt, Aetna began to gather the information necessary to mail letters to affected members to explain the situation and provide additional resources. Although Aetna is not aware of any evidence to indicate improper use of member information, Aetna is offering each affected member two years of credit monitoring coverage, at no cost,.BenefitMall notified Aetna that the breach was caused by phishing attacks, which occurred between approximately June 2018 and October 19, 2018, and have since been contained. BenefitMall informed Aetna that the affected correspondence may have included names, addresses, Social Security numbers, dates of birth, zip codes, bank account numbers, plan descriptions, premium payment amounts, and health plan beneficiary numbers.

If members have any questions, they can call Aetna toll-free at the number on the back of their member ID cards. 6285007


Related:

  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Gatineau gymnastics centre warns members of possible data breach
  • Data breach in 42 Latvian municipalities: DVI imposes 300,000 euro fine on ZZ Dats
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
Category: Breach IncidentsHealth DataPhishingSubcontractorU.S.

Post navigation

← Kansas hospital pays $250K to settle charges it falsified EHR security risk assessment
Ellwood City Medical Center Victim Of Cyber Attack, Not Sure If Patient Records Were Exposed →

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.