[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fVniEEezFKkg1JN6SfibfBPcTiQJcl63x0gSTPBdHp94":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"company":11,"breachDate":15,"addedDate":16,"modifiedDate":16,"pwnCount":17,"totalRecords":17,"dataClasses":18,"description":36,"source":37,"isVerified":4,"isSpamList":38,"isSensitive":4,"severity":39,"processingStatus":40,"logoUrl":41,"contentUpdatedAt":16,"hasEnglishDescription":4},"6a66ef456b96c4b593415db9","Lifespark2026","Lifespark 2026 Data Breach","lifespark-2026","lifespark.com",{"name":12,"sector":13,"country":14,"website":10},"Lifespark Management Services, Inc.","Healthcare","United States","2026-02-18T00:00:00.000Z","2026-07-27T05:40:21.029Z",0,[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"Personal information","Protected health information","Names","Dates of birth","Driver's license numbers","State identification numbers","Financial account information","Payment card information","Social Security numbers","Passport numbers","Treatment information","Diagnosis information","Disability information","Medical record numbers","Provider information","Prescription information","Health insurance information","\u003Cp>\u003Cstrong>The Lifespark 2026 data breach\u003C\u002Fstrong> was an unauthorized-access incident discovered when the Minnesota-based senior-care and health-services organization identified suspicious activity in its email environment on or about February 18, 2026. Lifespark Management Services’ official notice confirms that certain information in the email environment was accessed without authorization for a limited period.\u003C\u002Fp>\n\u003Cp>Public sources have not disclosed the total number of affected people, and the event does not appear in HHS OCR’s current list of breaches affecting 500 or more people as of July 27, 2026. pwnCount and totalRecords are therefore zero; this does not mean nobody was affected. LeakData imported no person rows, and importedRecordCount is zero.\u003C\u002Fp>\n\u003Ch2>How Was the Lifespark Breach Confirmed?\u003C\u002Fh2>\n\u003Cp>The primary source is the Notice of Data Event dated July 24, 2026 and published on Lifespark’s own domain. The one-page official document directly explains the discovery date, unauthorized email-environment access, forensic review, data categories, assistance line, and recommended identity-theft precautions.\u003C\u002Fp>\n\u003Cp>The second source is Claim Depot’s July 26, 2026 report. Using the company notice and linked document, it independently describes the email-environment incident, person-by-person review, and potentially affected categories of personal, financial, and health information. This entry makes no unsupported attribution to an attacker or ransomware group.\u003C\u002Fp>\n\u003Ch2>What Was Discovered on February 18, 2026?\u003C\u002Fh2>\n\u003Cp>Lifespark identified suspicious activity in its email environment on or about February 18. The organization acted to address and investigate the event and engaged third-party computer-forensics specialists to help establish the nature and scope of the unauthorized activity.\u003C\u002Fp>\n\u003Cp>The investigation found that certain information was subject to unauthorized access for a limited period, but the first and last days of access were not published. The breachDate field uses February 18, 2026, the disclosed discovery date, not a confirmed access start. This entry creates no access duration or data-download claim absent from the sources.\u003C\u002Fp>\n\u003Ch2>What Personal Information May Have Been Affected?\u003C\u002Fh2>\n\u003Cp>The fields varied by person and may include a name together with a date of birth, driver’s-license or state-identification number, financial-account information, payment-card information, Social Security number, or passport number. This combination is highly sensitive for identity theft, account fraud, and targeted social engineering.\u003C\u002Fp>\n\u003Cp>The official notice does not say every field belonged to every person and provides no affected-person count. This entry therefore creates no field-level subgroup totals. Because the sources disclose no passwords, usernames, or biometric data, those categories are not added; download or public release of emails or attachments has not been confirmed.\u003C\u002Fp>\n\u003Ch2>What Health Information Was Involved?\u003C\u002Fh2>\n\u003Cp>Potential protected health information may include treatment, diagnosis, and disability information; medical-record numbers; provider information; prescription information; and health-insurance information. Lifespark provides senior living, home health, hospice, primary care, and transportation services, making these fields particularly important for medical-identity fraud.\u003C\u002Fp>\n\u003Cp>The company did not disclose which service line or population produced the affected email data. This entry therefore creates no counts or definitive scope for patients, employees, providers, or family members. It also does not assume that diagnosis, prescription, or insurance fields belonged to every person; it reports only the possible categories in the official notice.\u003C\u002Fp>\n\u003Ch2>Why Is the Affected-Person Count Shown as Zero?\u003C\u002Fh2>\n\u003Cp>pwnCount and totalRecords remain zero because no verified public source provides an affected-person total. Zero does not mean the event was small, harmless, or involved no individual; it is a technical unknown value showing that LeakData did not invent a number absent from the evidence.\u003C\u002Fp>\n\u003Cp>Lifespark’s investigation required a comprehensive and time-consuming person-by-person review to identify the information and people involved. The company began notification and published its general notice on July 24. If a regulatory total is later disclosed, this entry should be updated rather than creating a new duplicate for the same event.\u003C\u002Fp>\n\u003Ch2>What Should Potentially Affected People Do?\u003C\u002Fh2>\n\u003Cp>People should regularly review bank and payment-card accounts, credit reports, health-insurance explanation-of-benefits statements, prescription histories, and medical-service records for unfamiliar activity. If an unknown transaction or service appears, the relevant organization should be contacted through a verified channel; a fraud alert or free credit freeze may also be appropriate.\u003C\u002Fp>\n\u003Cp>Social Security numbers, passports, payment cards, or health information should not be shared through unexpected links or calls claiming to represent Lifespark. Questions can be initiated through the 1-866-898-3999 number in the company notice. LeakData does not host, distribute, or provide search access to email content, personal records, or health data.\u003C\u002Fp>","Official Lifespark notice confirming unauthorized access within its email environment",false,"Low","completed","\u002Fuploads\u002Flogo\u002Flifespark_com.png"]