[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fXrMa5Z_tYAuGytLyvVjWrnNft6pVCWHXPF8OXQMRkbM":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":29,"source":30,"isVerified":4,"isSpamList":31,"isSensitive":4,"severity":32,"processingStatus":33,"logoUrl":34,"contentUpdatedAt":16,"hasEnglishDescription":4},"6a670139958ad06faa32e335","AdamsHealthNetwork2026","Adams Health Network 2026 Data Breach","adams-health-network-2026","adamshospital.org",{"name":12,"sector":13,"country":14,"website":10},"Adams Health Network \u002F Adams Memorial Hospital","Healthcare","United States","2025-12-22T00:00:00.000Z","2026-07-27T06:56:57.882Z",5305,[19,20,21,22,23,24,25,26,27,28],"Personal information","Protected health information","Names","Addresses","Dates of birth","Social Security numbers","Dates of service","Diagnosis information","Charge information","Insurance information","\u003Cp>\u003Cstrong>The Adams Health Network 2026 data breach\u003C\u002Fstrong> was a confirmed security incident caused by phishing that compromised an employee email account at the Indiana health network operating Adams Memorial Hospital. The organization discovered the event on March 12, 2026; an independent chronology and regulatory data place the start of unauthorized access on December 22, 2025.\u003C\u002Fp>\n\u003Cp>The U.S. Department of Health and Human Services Office for Civil Rights lists the Adams County Memorial Hospital event as a Hacking\u002FIT Incident affecting 5,305 people. LeakData imported no patient or person rows, and importedRecordCount is zero. This entry is verified through the official company notice, federal HHS record, and a reliable summary incorporating Indiana regulatory data.\u003C\u002Fp>\n\u003Ch2>How Was the Adams Health Network Breach Confirmed?\u003C\u002Fh2>\n\u003Cp>The primary source is the Notice of Cybersecurity Incident published on Adams Memorial Hospital's own website. It directly explains that phishing compromised an employee email account, identifies patient information in the account, states which systems were not affected, describes security steps taken, and outlines protection resources offered to patients.\u003C\u002Fp>\n\u003Cp>The HHS OCR record classifies the organization as an Indiana healthcare provider and reports 5,305 people, a May 11, 2026 submission date, an email location, and a hacking\u002FIT incident type. Claim Depot gives the current total of 5,305, including 3,594 Indiana residents, alongside the official notice and state record.\u003C\u002Fp>\n\u003Ch2>How Was the December 22, 2025 Date Determined?\u003C\u002Fh2>\n\u003Cp>The official web page says the email account was compromised on “December 22, 2026,” yet the same page says the event was discovered on March 12, 2026 and was published on May 11, 2026. A future compromise could not have been discovered earlier, so the year in that sentence is an evident typographical error.\u003C\u002Fp>\n\u003Cp>The independent chronology and Indiana reporting data identify December 22, 2025 as the start. LeakData uses that chronologically consistent date in breachDate and documents the official-page error in its source note. Because the exact end of access is not publicly stated, the March 12 discovery date is not automatically treated as the final access date.\u003C\u002Fp>\n\u003Ch2>Which System Was the Event Limited To?\u003C\u002Fh2>\n\u003Cp>The phishing attack affected one employee email account. Adams Health Network secured the account and ensured that the attacker no longer had access. The official notice specifically says the attacker did not access the organization's electronic medical record or any financial-account information, an important boundary for accurately evaluating scope.\u003C\u002Fp>\n\u003Cp>An email location does not prove that the entire organizational network or every mailbox was compromised. The source confirms only that messages or attachments in the involved employee account contained some patient information. LeakData does not expand the event into a network-server, full-EHR, or financial-system breach and does not guess the undisclosed phishing technique.\u003C\u002Fp>\n\u003Ch2>What Information May Have Been Affected?\u003C\u002Fh2>\n\u003Cp>The official list includes names, addresses, dates of birth, Social Security numbers, dates of service, diagnoses, charges, and insurance information. These fields can create identity-theft, fraudulent-account, targeted-impersonation, and medical-identity risks, but combinations vary by person and the record does not claim that every field applied to all 5,305 people.\u003C\u002Fp>\n\u003Cp>The “charges” field may describe the billed value of healthcare services; the official statement denies access to bank accounts or payment-card information. LeakData does not equate charge data with a financial-account number. Driver's licenses, passports, passwords, prescriptions, and detailed laboratory results are omitted because the source does not list them.\u003C\u002Fp>\n\u003Ch2>How Did the Organization Respond?\u003C\u002Fh2>\n\u003Cp>Adams Health Network secured the account, changed the involved employee's password, implemented additional organization-wide security protocols, and expanded employee education against future phishing attempts. It reported no evidence that the attacker was seeking patient information and no indication that patient data had been or would be used inappropriately.\u003C\u002Fp>\n\u003Cp>Affected people were offered 12 months of complimentary credit monitoring through CyberScout. The organization recommends monitoring healthcare accounts for suspicious or unusual activity and reporting possible fraud to the insurer or healthcare provider. A weekday assistance line was established at 877-791-2689.\u003C\u002Fp>\n\u003Ch2>What Should Affected People Do?\u003C\u002Fh2>\n\u003Cp>Recipients should regularly review credit reports, insurance explanation-of-benefits statements, medical bills, and patient portals. If an unknown date of service, diagnosis, charge, insurance claim, or credit account appears, the relevant organization should be contacted through a verified channel; a free fraud alert or credit freeze may be appropriate for SSN risk.\u003C\u002Fp>\n\u003Cp>SSNs, dates of birth, or insurance details should not be shared in unexpected email, text messages, or calls claiming to represent Adams Health Network or CyberScout, and enrollment codes in individual letters should not be given to others. LeakData does not host, distribute, or make searchable any email content, patient information, or identity numbers.\u003C\u002Fp>","Official Adams Health Network notice confirming phishing-related employee email compromise involving patient information",false,"Low","completed","\u002Fuploads\u002Flogo\u002Fadamshospital_org.png"]