[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fl1wUAFnkNzuW-v3ZYLL8v9p24MnK-dsgMTnuNelurfE":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"company":11,"breachDate":15,"addedDate":16,"modifiedDate":17,"pwnCount":18,"totalRecords":18,"dataClasses":19,"description":26,"source":27,"isVerified":4,"isSpamList":28,"isSensitive":4,"processingStatus":29,"logoUrl":30,"contentUpdatedAt":17,"hasEnglishDescription":4,"severity":31},"6a675cd3d77e874d70fcb590","AnchorageNeighborhoodHealthCenter2025","Anchorage Neighborhood Health Center 2025 Data Breach","anchorage-neighborhood-health-center-2025","anhc.org",{"name":12,"sector":13,"country":14,"website":10},"Anchorage Neighborhood Health Center","Healthcare","United States","2025-10-10T00:00:00.000Z","2026-07-27T13:27:47.052Z","2026-07-27T16:11:11.968Z",70555,[20,21,22,23,24,25],"Names","Dates of birth","Social Security numbers","Driver’s license or state identification numbers","Medical treatment information","Health insurance information","\u003Cp>\u003Cstrong>The Anchorage Neighborhood Health Center 2025 data breach\u003C\u002Fstrong> was a criminal cyberattack affecting systems at the Alaska community health center. ANHC worked with third-party experts to secure its systems and investigate the scope. Around October 10, 2025, the organization determined that some personal and protected health information may have been subject to unauthorized access or acquisition.\u003C\u002Fp>\n\u003Cp>The U.S. The affected-person or record count published by the official source represents the reported scope of the incident. It does not mean that every disclosed data category applied to every person.\u003C\u002Fp>\n\u003Ch2>How Was the ANHC Breach Confirmed?\u003C\u002Fh2>\n\u003Cp>The primary source is the Data Incident Notification published on ANHC's own domain. The PDF directly describes the criminal cyberattack, October 10 scope determination, possible data types, an offer of at least 12 months of Experian credit monitoring, cybersecurity enhancements, and the 1-844-976-2439 assistance line.\u003C\u002Fp>\n\u003Cp>The second source is the official HHS\u002FOCR entry dated November 19 for 70,555 people. ClaimDepot's incident page independently cross-checks the same event through links to the organization notice, federal total, and multiple state disclosures. Unverified person counts, data fields, and threat-actor claims are not treated as part of the public incident scope.\u003C\u002Fp>\n\u003Ch2>What Does the October 10, 2025 Date Mean?\u003C\u002Fh2>\n\u003Cp>ANHC's official text does not disclose the precise first-access date. It says that during its extensive investigation, the organization determined around October 10 that the incident may have affected PHI or PII related to certain people.\u003C\u002Fp>\n\u003Cp>November 19 in the HHS row is the federal portal report date, not the beginning of the incident. Later publication and update dates on the ClaimDepot page belong to its content workflow. The access window, initial entry method, actor identity, and exact time of any data acquisition are not stated in the organization notice and are not guessed here.\u003C\u002Fp>\n\u003Ch2>What Information May Have Been Involved?\u003C\u002Fh2>\n\u003Cp>The official notice says the incident may have affected names, dates of birth, Social Security numbers, driver's license or state identification numbers, medical-treatment information, and health-insurance information. Its “and\u002For” language means scope may differ by person; it should not be assumed that every field was present for every record holder.\u003C\u002Fp>\n\u003Cp>The document does not break treatment or insurance information into narrower diagnosis, medication, procedure, policy, or claim-number fields. Possible unauthorized access or acquisition is confirmed, but the record does not claim every field was viewed or misused.\u003C\u002Fp>\n\u003Ch2>How Should the Affected-Person Count Be Interpreted?\u003C\u002Fh2>\n\u003Cp>70,555 is the affected-person count published in the HHS\u002FOCR portal; it is not a file, document, or attacker-listed row count. The affected-person or record count published by the official source represents the reported scope of the incident. It does not mean that every disclosed data category applied to every person.\u003C\u002Fp>\n\u003Cp>Local resident counts in state attorney-general disclosures are subsets of the nationwide total. Those subsets are not added to 70,555 because doing so would count the same individuals twice.\u003C\u002Fp>\n\u003Ch2>What Are the Identity and Medical-Fraud Risks?\u003C\u002Fh2>\n\u003Cp>A name combined with a date of birth, SSN, and government identification number can increase the risk of impersonation, fraudulent credit applications, and personalized phishing. Treatment and health-insurance information may be used in false service, claim, or billing attempts. Possible exposure does not prove misuse occurred, but it may justify long-term monitoring.\u003C\u002Fp>\n\u003Cp>Users should review health-insurance Explanation of Benefits statements as well as credit reports and financial accounts. An unfamiliar treatment, provider, or payment should be verified directly with the insurer and healthcare organization. Unexpected communications claiming to represent ANHC should not receive a full SSN, identification number, password, payment information, or one-time code.\u003C\u002Fp>\n\u003Ch2>What Did ANHC Do and What Can Recipients Do?\u003C\u002Fh2>\n\u003Cp>ANHC said it secured systems with third-party experts, conducted a scope review, and implemented a series of cybersecurity enhancements after the incident. Potentially affected individuals were offered at least 12 months of free Experian credit monitoring and related services. Each person should rely on their own notice for enrollment terms and individual data scope.\u003C\u002Fp>\n\u003Cp>People can ask questions or determine whether they were potentially affected by calling 1-844-976-2439 on weekdays from 6:00 a.m. to 6:00 p.m. Pacific Time. Recipients may activate credit monitoring, consider a fraud alert or free credit freeze where appropriate, and promptly report suspicious financial or medical activity to the relevant institution. If a suspicious message or account event appears, it should be verified through the organization’s current official contact channel without using links in the message. When an individual notification letter is available, it is the primary source for the person-specific data scope and protection options offered.\u003C\u002Fp>","ANHC official notice, HHS\u002FOCR report, and state-linked incident reporting",false,"completed","\u002Fuploads\u002Flogo\u002Fanhc_org.webp","Medium"]