All Breaches
June 1, 2023 Verified Sensitive Record Healthcare / Medical imaging

Longhorn Imaging Center (2023) Data Breach

The Longhorn Imaging Center data breach is a high-sensitivity health data incident associated with the patient portal access during June 2023, examined in the context of the U.S.-based medical imaging service linked to the domain longhornimaging.com.

100.6 Thousand
Reported Records
6
Data Types
High
Severity
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

2 sensitive6
  • Personal health data
  • Health insurance information
  • Names
  • Dates of birth
  • Genders
  • Physical addresses

About This Breach

This record was included because it is supported as a single incident affecting approximately 100,643 individuals in official notifications. The record contained first and last names, dates of birth, gender information, physical addresses, personal health information, and health insurance details; unsupported claims of payment card, bank account, password, or social security number were excluded to avoid misleading the user.

Leaked Data Types and Risks

In the verification assessment, the name Longhorn Imaging Center, the domain longhornimaging.com, the context of Texas healthcare services, the event timing in June 2023, the official notification at the level of 100,643 individuals, and the health data fields that could have been accessed through the patient portal were considered together. Although some leak directories claimed approximately 272,000 record lines, this number was not directly used as the number of uniquely affected individuals. A more conservative value of 100,643, close to the official notification, was used for the number of affected individuals; the explanation was limited to avoid confusing the total record volume with the number of affected individuals.

Verified Scope and Boundaries

The Longhorn Imaging Center data breach creates risks for users in terms of health privacy, authentication, and targeted fraud. When name, date of birth, gender, address, and healthcare context are combined, attackers can craft messages themed around appointments, imaging results, insurance verification, billing, patient portal updates, or document sharing. Because users in healthcare settings already expect appointment and document notifications, such messages may appear more convincing. Therefore, the incident should be evaluated not only as a communication data risk but also as a health privacy and social engineering risk.

User Groups at Risk

In this incident, visible data categories are considered sensitive because the healthcare context can provide indirect information about a person's treatment process, institutional relationship, or insurance flow. The record was not expanded as if it contained specific diseases, imaging results, or detailed clinical content; however, the mere presence of health information and insurance information fields provides sufficient context for phishing and fraud. Users should not automatically trust callers who know their correct name, date of birth, address, or healthcare institution information, and should verify each request through an independent channel.

Individuals who may be associated with Longhorn Imaging Center should check for unusual notifications in patient portals, email, insurance, and financial accounts. Unexpected bills, insurance updates, appointment confirmations, imaging results, document downloads, or patient portal password reset links should be verified directly through known official channels. One-time codes, identification documents, payment information, or insurance number requests received by phone should not be shared. In messages that appear to come from a healthcare provider, the known address or phone number of the institution should be used instead of links.

Urgent Measures to Be Taken

From the perspective of institutions, the Longhorn Imaging Center data breach highlights the need for additional controls in patient portal and third-party health technology access. When fields such as patient name, date of birth, address, and insurance information are considered compromised, it is not safe to perform identity verification with just this information. Healthcare institutions should implement multi-factor authentication, session monitoring, and suspicious behavior auditing in processes such as portal access, document download, bill payment, insurance verification, and changes to patient contact information. Employees should be informed that health-related social engineering messages can be highly persuasive.

Long-Term Security Strategies

In the Longhorn Imaging Center data breach record, the scope was deliberately limited to the areas supported. The record was kept with a value of 100,643 affected individuals; higher row counts seen in different locations were not recorded as the number of users. The record was not expanded as if it contained payment card, bank account, password, or social security numbers. Nevertheless, the combination of name-surname, date of birth, address, health information, and insurance information carries high sensitivity. Even a small volume of health data records can have more serious consequences in terms of impact than large communication lists.

Record Control and User Action

The overall risk level has been assessed as critical because the Longhorn Imaging Center data breach combines healthcare relationships with identity and insurance areas. The most practical steps for users searching for the Longhorn Imaging Center data breach are to directly check the official patient portal, independently verify unexpected health and insurance messages, enable additional verification on their email account, approach links requesting payment or documents cautiously, and not consider searches starting with health information as trustworthy. The notice has been prepared to disclose health privacy without exaggeration but without diminishing its risk.

In the additional source comparison, the patient gender field has been re-added to the data classes since it is also supported in the context of health records. Details such as treatment date, institution name, or physician name have not been expanded as a separate class; they have been evaluated within personal health data that explains the context of the health service. In this way, the record maintains the number of affected individuals supported in official notifications while more accurately showing the scope of leaked data fields without misleading the user.

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