Innovative Scientific Solutions 2025 Data Breach
The Innovative Scientific Solutions 2025 data breach affected the network environment of the healthcare laboratory operating as Luxor Scientific.
Exposed Data Types
1 sensitive3- Medical information
- Personal information
- Social security numbers
About This Breach
The company said it learned on 6 September 2025 that certain systems were affected and, after a forensic investigation and document review, determined on 31 March 2026 that files potentially accessed or acquired by an unauthorized party contained personal information. Notifications began on 7 April 2026.
The U.S. Department of Health and Human Services record classifies the report submitted on 17 April 2026 as a healthcare-provider, network-server, hacking/IT incident affecting 143,842 people. This is not a count of online accounts, file rows, or records containing every field together. The 15,283 people listed by South Carolina are a state subset of the national total and are not added to it. Production has no local person-level import linked to the incident.
Verified data scope
The first-party notice supports that personal information was in the affected files, that some individuals had Social Security numbers in scope, and that medical information was involved. The public notice does not provide a complete detailed list covering names, birth dates, driver's licenses, cards, bank data, insurance policy numbers, prescriptions, diagnoses, or treatments. The previous broad field list is therefore narrowed; only a recipient's own notice can identify the fields involved for that person. The company said it had no indication of incident-related fraud as of the notice.
Evidence boundary and safe next steps
The sources do not identify the unauthorized party, initial-access method, access window, or whether files were definitively acquired; the company uses “potentially accessed and/or acquired.” A notified person should first check the person-specific field list. If a Social Security number was involved, the offered monitoring service, credit reports, a fraud alert, or a credit freeze may be considered. If medical information was involved, health-insurance explanations and health records can be reviewed for unfamiliar services. A match does not establish that every field was involved or prove a particular diagnosis, test, or treatment.
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