High Point Treatment Center 2025 Data Breach
The High Point Treatment Center 2025 data breach concerns unusual activity detected in the organization's network environment. According to High Point's official notice, it became aware of the event on or about 6 July 2025.
Exposed Data Types
3- Names
- Social security numbers
- Dates of birth
About This Breach
An investigation with legal counsel and external forensic specialists found that some information may have been viewed and copied by an unauthorized person. The affected-data review concluded on 17 July, and the notice letter was sent on 29 July.
HHS/OCR lists 25,832 affected people for High Point Treatment Center, Inc. and classifies the event as a hacking or IT incident involving an electronic medical record and network server. The official letter does not disclose the first access date, access duration, or technical method. The HHS system-location classification does not by itself establish that patient-data fields were involved.
What information may have been involved?
The official letter limits the possible fields to names, Social Security numbers, and dates of birth and says they were collected in connection with current or prospective employment at High Point. The combination varied by person; it does not follow that all three fields applied to all 25,832 people. Public sources do not list diagnoses, treatment, health insurance, financial accounts, or patient numbers. This event page also does not establish that a particular person was a High Point employee, applicant, or service recipient.
Organization response and safe next steps
High Point said it investigated the nature and scope, was not aware at the letter date of actual or attempted use of the information to commit fraud, and offered affected people 24 months of credit monitoring and fraud assistance. Because the enrollment period in the old letter may have passed, current eligibility should be verified through the organization's official channel. People whose notice lists a Social Security number can review credit reports for unfamiliar accounts or inquiries and consider a fraud alert or credit freeze. Full identification numbers, enrollment codes, passwords, and one-time codes should not be shared through unexpected messages.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
