Mom’s Meals Data Breach Sparks Legal Battle,1.2M Affected


In the wake of a recent Mom’s Meals data breach, Purfoods LLC now faces a formidable class action lawsuit, as the exposed personal health information of 1.2 million individuals stirs concerns.

Clyde Burry, the plaintiff, has initiated legal proceedings, raising concerns over the security incident’s implications.

The lawsuit alleges that Mom’s Meals failed to protect the information of 1.2 million individuals whose personal health information has been accessed by hackers.

The legal proceedings were initiated in a federal court in Iowa, shedding light on the severity of the Mom’s Meals data breach.

Individuals impacted by the Mom’s Meals data breach are encouraged to join a class action investigation. With the personal data of 1.2 million individuals on the line, the lawsuit is expected to intensify significantly from this juncture.

Mom’s Meals data breach Leads to lawsuit

Clyde Burry’s lawsuit contends that Mom’s Meals data breach notice failed to provide the correct information to the victims and affected parties.

This situation leaves these individuals vulnerable to potential targeting by threat actors, given the compromise of their health data in the breach.

The lawsuit also states that the parent company, PurFoods, failed to provide any information about the ransomware that infiltrated the company. 

Failing under the purview of the Health Insurance Portability and Accountability Act (HIPAA), Mom’s Meals will be facing a strict lawsuit since it failed to protect the personal health information of its customers.

According to the lawsuit, HIPAA egulations mandate the company to have notified each affected individual within 60 days of discovering the breach.

Mom’s Meals data breach: What Happened?

Mom’s Meals, an online service specializing in delivering meals to individuals with chronic health conditions, disclosed a data breach last month. The company acknowledged that the breach has the potential to impact its users.

According to the official release, the Mom’s Meals data breach occurred between January 16 and February 22 this year, and the same was reported to Maine’s attorney general by PurFoods, the parent company of Mom’s Meals.

According to PurFoods, the Mom’s Meals data breach led to the encryption of various documents, files, and folders related to the company, with a particular focus on customer information.

Furthermore, the investigation of the Mom’s Meals data breach uncovered evidence of data theft tools and techniques within the network. However, the official release did not specify any particular threat actor responsible for the breach

The Mom’s Meals data breach is believed to be a potential ransomware attack, where threat actors stole the company’s data by exploiting a vulnerability. The company acknowledged that data might have been extracted from one of their file servers.

Incident response team to tackle Mom’s Meals data breach

According to PurFoods, the company had employed a third-party Incident response team to look into the Mom’s Meals data breach.

The investigation concluded in July, and the company discovered that sensitive customer data and information about protected health datasets of individuals were compromised. 

Moreover, the Mom’s Meals data breach also affected multiple alleged victims, including but not limited to customers of Mom’s Meals data breach members with or without health plans.

The company employees are also subjected to the breach, including all the current and former employees. 

The exposed information encompassed a range of sensitive data such as customer names, Social Security numbers, driver’s license and state identification numbers, financial account details, payment card information, medical record numbers, treatment and diagnosis information, and more.

Media Disclaimer: This report is based on internal and external research obtained through various means. The information provided is for reference purposes only, and users bear full responsibility for their reliance on it. The Cyber Express assumes no liability for the accuracy or consequences of using this information.





Source link