[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ffr4CowwKnU7ZULCFi0sQhcN-o7J391GXAj8G9J2zjfw":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":39,"source":40,"isVerified":4,"isSpamList":41,"isSensitive":4,"processingStatus":42,"logoUrl":43,"contentUpdatedAt":16,"hasEnglishDescription":4,"severity":44},"6a675e54897f3b628947b367","PersanteHealthCare2025","Persante Health Care 2025 Data Breach","persante-health-care-2025","persante.com",{"name":12,"sector":13,"country":14,"website":10},"Persante Health Care","Healthcare","United States","2025-01-23T00:00:00.000Z","2026-07-27T13:34:12.070Z",111815,[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"Names","Dates of birth","Social Security numbers","Driver’s license numbers","State identification numbers","Passport numbers","Government identification numbers","Individual Taxpayer Identification Numbers","Dates of medical service","Physician or medical facility information","Medical condition or treatment information","Medical diagnosis information","Medicare or Medicaid numbers","Health insurance policy numbers","Financial account numbers","Payment card numbers","Patient account numbers","Medical record numbers","Medical device identifiers","Biometric identifiers","\u003Cp>\u003Cstrong>The Persante Health Care 2025 data breach\u003C\u002Fstrong> involved an unknown actor gaining unauthorized access to the sleep- and balance-center management provider's network between January 23 and 28, 2025. Persante detected unusual network activity around January 28. Its investigation found that certain files may have been accessed or acquired and may have contained personal or protected health information.\u003C\u002Fp>\n\u003Cp>The U.S. Department of Health and Human Services Office for Civil Rights portal lists 111,815 affected individuals for Persante Health Care and classifies the event as a network-server “Hacking\u002FIT Incident.” This official person total is used in pwnCount and totalRecords. importedRecordCount is zero because no raw person-level data was obtained.\u003C\u002Fp>\n\u003Ch2>How Was the Persante Breach Confirmed?\u003C\u002Fh2>\n\u003Cp>The primary document is Persante's “Data Security Incident” notice dated November 26, 2025. The archived PDF describes the January 23–28 access window, January 28 discovery, October 3 scope determination, possible access or acquisition of files, extensive data classes, FBI notification, consumer mailings, and the 844-354-1778 assistance line.\u003C\u002Fp>\n\u003Cp>The second source is the official HHS\u002FOCR row dated November 26 for 111,815 people. ClaimDepot's incident page independently connects the same notice, HHS total, and state disclosures. LeakData does not carry the attacker name mentioned by a secondary source into the primary record because the organization's official text describes an “unknown actor.”\u003C\u002Fp>\n\u003Ch2>What Happened Between January 23 and 28, 2025?\u003C\u002Fh2>\n\u003Cp>When Persante detected unusual network activity around January 28, it secured the network and began an investigation with external cybersecurity experts. The investigation uncovered information suggesting that an unknown actor had unauthorized access from January 23 through January 28 and may have accessed or acquired certain files.\u003C\u002Fp>\n\u003Cp>The organization then comprehensively reviewed the potentially affected data and determined around October 3 that certain individuals' personal or protected health information may have been involved. It coordinated notification work with affected medical facilities, verified information and addresses, and mailed letters November 26 to people for whom an identifiable address was available.\u003C\u002Fp>\n\u003Ch2>What Information May Have Been Involved?\u003C\u002Fh2>\n\u003Cp>The official notice lists names, dates of birth, Social Security numbers, driver's license numbers, state identification numbers, passport numbers, other government identification numbers, and Individual Taxpayer Identification Numbers. It also lists dates of medical service, physician or facility information, medical condition or treatment, diagnosis, Medicare or Medicaid numbers, and individual health-insurance policy numbers.\u003C\u002Fp>\n\u003Cp>Financial-account numbers, payment-card numbers, patient-account numbers, medical-record numbers, medical-device identifiers, and biometric identifiers also appear in the official list. Scope varies by individual; it should not be assumed that every field was present for every person or that the actor acquired every file. This record preserves the notice's “may have been involved” and “potentially accessed or acquired” boundaries.\u003C\u002Fp>\n\u003Ch2>How Should 111,815 People and Zero Imports Be Read?\u003C\u002Fh2>\n\u003Cp>111,815 is the affected-person count published for this event in the HHS\u002FOCR portal. It is not a file count, attacker-listed row volume, or number of accounts transferred into LeakData. pwnCount and totalRecords show the official person total, while importedRecordCount 0 means no raw, searchable person-level records were imported.\u003C\u002Fp>\n\u003Cp>Local resident counts in state disclosures are subsets of the nationwide total and are not added to 111,815. Likewise, the medical facilities served by Persante may be separate organizations, but Persante's HHS row is retained as one regulatory incident total. This prevents the same people or the same event from being counted twice.\u003C\u002Fp>\n\u003Ch2>What Are the Identity, Health, and Financial Risks?\u003C\u002Fh2>\n\u003Cp>SSNs, passports, tax identifiers, and government identification can increase impersonation and fraudulent-account risks. Medical and insurance fields may be used in false service or claim attempts, while financial-account and payment-card information may support payment fraud. Biometric identifiers can warrant especially careful, long-term monitoring because they cannot be changed like a password.\u003C\u002Fp>\n\u003Cp>Recipients should review Explanation of Benefits documents in addition to credit reports, financial accounts, and card activity. An unexpected message claiming to represent Persante or a medical facility should not receive a full SSN, identification number, payment information, password, or one-time code. An unfamiliar medical service or financial transaction should be verified directly with the relevant institution.\u003C\u002Fp>\n\u003Ch2>What Did Persante Do and What Can Recipients Do?\u003C\u002Fh2>\n\u003Cp>Persante said it secured the network, performed a scope review with external experts, notified the FBI, and took additional steps intended to prevent a similar event. Notifications were coordinated with medical facilities, and people were mailed information about the incident and protective measures. The organization does not make a blanket statement that misuse definitely occurred.\u003C\u002Fp>\n\u003Cp>The call center at 844-354-1778 is available weekdays from 9:00 a.m. to 6:30 p.m. Eastern Time. A person should treat their own notification letter as the primary source for their individual data scope and report suspicious activity to the relevant financial institution, healthcare provider, or law-enforcement agency. A fraud alert or free credit freeze may also be considered when appropriate.\u003C\u002Fp>","Persante official notice, HHS\u002FOCR report, and state-linked incident reporting",false,"completed","\u002Fuploads\u002Flogo\u002Fpersante_com.png","High"]