[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fns8e93jgafrf":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":12,"modifiedDate":13,"contentUpdatedAt":13,"source":14,"sourceUrl":15,"sourceUrls":16,"pwnCount":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":12,"affectedCountUnit":20,"hasEnglishDescription":4,"contentLocale":21,"availableLocales":22,"translations":24,"severity":27,"dataClasses":28,"description":40,"seoTitle":41,"seoDescription":42,"logoUrl":43,"isVerified":4,"isSensitive":4,"isSpamList":44,"isMalware":44,"company":45},"6a4f993aab07cf3fffce5f47","Gryphon Healthcare 2024","Gryphon Healthcare 2024 Data Breach","gryphon-healthcare-2024","gryphonhc.com","2024-07-06T00:00:00.000Z",null,"2026-07-29T11:13:00.741Z","Official Gryphon notice and California regulator filing","https:\u002F\u002Fwww.gryphonhc.com\u002Fwp-content\u002Fuploads\u002F2024\u002F11\u002FData-Security-Incident.pdf",[15,17],"https:\u002F\u002Foag.ca.gov\u002Fecrime\u002Fdatabreach\u002Freports\u002Fsb24-593262",393358,"known","people","en",[21,23],"tr",{"en":25,"tr":26},{"slug":9},{"slug":9},"High",[29,30,31,32,33,34,35,36,37,38,39],"Names","Dates of birth","Physical addresses","Social Security numbers","Dates of service","Diagnoses","Health insurance information","Treatment information","Prescription information","Provider information","Medical record numbers","\u003Cp>\u003Cstrong>The 2024 Gryphon Healthcare breach\u003C\u002Fstrong> involved unauthorized access to personal and protected-health-information files Gryphon maintained in an incident involving a partner for which it provided medical-billing services. A California filing gives July 6, 2024 as the known breach date. Gryphon learned of the event on August 13, completed its file review on September 3, and mailed notices on October 11.\u003C\u002Fp>\u003Cp>The organization said current and former patients may have been affected and that fields varied by person. Possible information included names, dates of birth, addresses, Social Security numbers, dates of service, diagnoses, health insurance, treatment, prescriptions, providers, and medical record numbers. “Protected health information” and generic “medical information” are not additional populations beyond the underlying fields.\u003C\u002Fp>\u003Cp>The company notice does not publish a count; later legal and reporting material describes approximately 393,358 potentially affected individuals. This is a notification population, not accounts, emails, corpus rows, or confirmed victims. Gryphon said it had no evidence of misuse as of the notice; that does not make later misuse impossible.\u003C\u002Fp>\u003Cp>There is no local person-level or PHI corpus. The event does not identify anyone as a current patient, holder of a particular diagnosis, treatment, or prescription, insured person, or recipient of a particular provider's services. Social Security and healthcare associations must remain private, and direct recipients should review credit or healthcare and insurance records only as relevant to the fields in their own letters.\u003C\u002Fp>","Gryphon Healthcare 2024 Data Breach (393.4 Thousand People Affected)","Gryphon Healthcare 2024 Data Breach. 393.4 Thousand people affected are reported. Reported data: Names, Dates of birth, Physical addresses. Review the scope…","\u002Fuploads\u002Flogo\u002Fgryphon-healthcare-2024.png",false,{"name":46,"sector":47,"country":48,"website":10,"websiteArchiveUrl":49,"websiteStatus":49,"websiteCheckedAt":12},"Gryphon Healthcare, LLC","Healthcare","United States",""]