DataBreaches.Net

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

Second verse, same as the first: Minuteman Senior Services reports another breach of an employee email account

Posted on February 14, 2023 by Dissent

Minuteman Senior Services (“MSS”) in Massachusetts notified the U.S. Department of Health and Human Services on January 27 that they experienced a breach affecting 500 patients. The “500” is simply a marker that indicates that the reporting entity knows they have to report a breach to HHS within 60 days of discovery but they do not yet really know how many patients were affected. They only know or estimate that it is more than the 500 trigger to report to HHS.

On their website, MSS writes that on November 30, 2022, they identified suspicious activity related to an employee’s email account. An investigation subsequently determined that the employee’s email account was accessed by an unknown individual between November 21 and November 30, 2022.

MSS has been working with an external data review specialist to identify any personal information in the account and to whom it applies. The types of information that may have been present in the compromised email account could have included: full name, address, date of birth, gender, health insurance information, diagnosis, and service utilization, although the exact data types may vary by individual.

“Once this comprehensive review is complete, MSS will then work to confirm the identities and contact information for potentially impacted individuals and provide notice via a written letter,” they write.

So as of January 27, they had not sent out letters or even completed figuring out who needed to be notified. There is no update on the site indicating whether letters have since gone out.

In response to the incident, MSS writes the usual affirmation of taking the incident and security very seriously:

Upon learning of this event, we immediately secured the impacted email account. As part of our ongoing commitment to the information security, we are enhancing our existing policies and procedures and implementing additional administrative and technical safeguards to further secure the information in our care.

The problem with that assurance, however, is that is exactly what they wrote back in July 2022, after an earlier incident involving the compromise of an employee’s email account. In their July notification, they wrote exactly the same description of their response.

Could the November 2022 compromise of the employee’s email account have been avoided? Was MFA deployed after the July incident? Was staff trained or retrained on phishing? Did all staff do password resets?  MSS did not disclose how the employee’s account was compromised in July, nor how an employee’s account was compromised in November. But HHS may consider whether MSS did enough after the first breach to prevent the second breach.

We will eventually learn how many patients the November breach affected. The July 2022 breach affected 4,000 patients.


Related:

  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Attorney General James Secures $14.2 Million from Car Insurance Companies Over Data Breaches
  • Months After Being Notified, a Software Vendor is Still Exposing Confidential and Sealed Court Records
Category: Breach Incidents

Post navigation

← If you’re going to “attack” a public school district, learn what FERPA permits districts to make public anyway
FL: Brooks Rehabilitation notifies patients of pixel tracking breach →

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

  • 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
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

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.