Scripps Data Breach
Published: Nov 10, 2026 Vortex
Threat Level
High
Confidence: High
Quick Summary
- Company
- Scripps Data Breach
- Industry
- Healthcare
- Threat Actor
- Vortex
- Date of Incident
- Nov 10, 2026
Executive Summary
Scripps, a healthcare organization operating in the United States, was listed on the dark web victim site of the Vortex ransomware group on 2026-11-10. SOCRadar’s Dark Web Team observed the listing through its dark web monitoring. The listing is significant given Scripps’s data profile: the organization holds patient, staff, and partner data, and US healthcare is a primary target sector for Vortex, placing Scripps directly within the sector focus the group has demonstrated in its recent activity. Vortex claimed approximately 14 victims over the 60 days preceding the Scripps listing. US healthcare stands out as a primary target sector for the group, and its recent victims include Arthrex (US, Healthcare), Andersen Construction (US, Manufacturing), Solenis (US, Manufacturing), and Karlstorz (DE, Healthcare). Scripps aligns closely with this pattern: the overlap is geographic, with most recent victims based in the United States, and sector-based, with healthcare organizations such as Arthrex and Karlstorz appearing alongside manufacturing victims. The Scripps listing is therefore consistent with Vortex’s current targeting behavior rather than an isolated or atypical claim.
Technical Analysis
SOCRadar’s credential correlation found 15 records tied to Scripps’s environment active in dark web datasets, with activity recorded as recently as 2026-11-09 — one day before the Vortex listing appeared. The finding is rated SEVERE. The records break down into 2 employee accounts (Category A: direct staff access to organizational systems) and 13 customer or supplier records (Category B: third-party access to organizational systems). The exposure window runs from 2026-10-21 through 2026-11-09, and the affected credentials span mixed corporate and patient-facing systems. Category A exposure is particularly consequential because internal accounts can bypass perimeter controls without triggering typical alerts. The correlation timeline materially strengthens the intrusion hypothesis. Vortex’s operational approach leans heavily on infostealer credential markets, using logs from stealers such as Lumma, RedLine, and Stealc sourced from dark web markets and Telegram to gain initial access with legitimate credentials. Credential records tied to Scripps remaining active in underground datasets the day before the listing therefore significantly elevates the probability of a credential-based intrusion path, although the telemetry alone does not prove these specific credentials were used for initial access. For executives and risk owners, the source assessment is explicit: treat this as a probable intrusion event rather than a precautionary listing, because the credential timeline argues for an escalated response posture. Given this assessment, the recommended response goes beyond passive monitoring. All credentials falling within the 2026-10-21 to 2026-11-09 exposure window should be reset immediately. Phishing-resistant multi-factor authentication should be enforced on every remote access point, with particular urgency on portals accessible to the 13 third-party (Category B) accounts. Privileged access assignments should be audited, and incident response capabilities engaged: the combination of the Vortex listing and the active credential signal warrants full IR escalation rather than a monitoring posture.
Disclaimer
This report is intended for threat intelligence and security awareness purposes. SOCRadar does not host, redistribute or buy stolen data. All breach information reported here is collected from publicly accessible threat actor and ransomware portals. This content is intended to equip CTI teams with context around recent attacks. While we strive for accuracy, listings on ransomware leak and extortion sites cannot always be independently verified and may not reflect confirmed breaches. If you believe any data in this report is incorrect, please contact us.
Share