Arthrex Data Breach
Published: Nov 19, 2026 Vortex
Threat Level
High
Confidence: High
Quick Summary
- Company
- Arthrex Data Breach
- Industry
- Healthcare
- Threat Actor
- Vortex
- Date of Incident
- Nov 19, 2026
Executive Summary
Arthrex, a U.S. healthcare company, was posted on the dark web leak site of the Vortex ransomware group on November 19, 2026. SOCRadar identified the listing through its Dark Web Monitoring service. The claim makes Arthrex one of 35 victims that Vortex has listed over the past 60 days, a notably high volume of claims for the group. Vortex’s recent victim list skews heavily toward Healthcare and Manufacturing, so the appearance of a U.S. healthcare organization on the leak site is consistent with the sectors the group has been concentrating on. As with all ransomware leak-site claims, the listing should be treated as alleged until it is independently verified or confirmed by the victim, since leak-site posts cannot always be validated and may not reflect confirmed breaches. Vortex’s claimed victims in recent weeks are concentrated in Healthcare and Manufacturing, with the United States, Germany, and Ireland featuring prominently in the group’s targeting. Arthrex sits at the center of that profile as a U.S. healthcare company. Other recent Vortex listings in the same sector or geography include Drive Medical, APELLIS Pharmaceuticals, Owens-Minor, and Caris Life Sciences, all of them U.S. healthcare or life sciences organizations. This cluster of related victims demonstrates strong geographic and sectoral overlap between Arthrex and the group’s recent operations. The claim against Arthrex therefore matches, rather than departs from, Vortex’s typical targeting pattern, which suggests the listing is part of a sustained campaign against U.S. healthcare and life sciences organizations.
Technical Analysis
SOCRadar queried stealer-log telemetry for arthrex[.]com in connection with the Vortex leak-site listing. The query returned no records in the sample, meaning no credentials tied to the domain surfaced in the stealer-log dataset at the time of the check. This result is an observation about the queried dataset only, and it does not confirm that Arthrex is unaffected. The absence of a positive signal is not a clean result, and it should not be interpreted as evidence that no compromise occurred. The result carries several limitations. The stealer-log query covers a paginated, bounded slice of the available data rather than the full corpus, so credentials could exist outside the sample that was checked. Credentials could also sit under a sibling domain or staff personal aliases not surfaced by a query scoped to arthrex[.]com, and records may exist in feeds outside the queried dataset. Credentials may additionally have been harvested and used before indexing, or may not yet have been indexed at the time of the query. Any of these scenarios could leave real exposure invisible to this particular check. Given these limitations, continued dark web and stealer-log monitoring is warranted so that newly indexed credentials linked to arthrex[.]com or related domains are detected as they appear. Proactive credential-hygiene checks, including password rotation where exposure is suspected and a review of multi-factor authentication coverage, would reduce the risk associated with any credentials the queried sample did not surface. Security teams should also monitor alternate corporate and sibling domains for matches, since credentials registered under those domains would not appear in a query limited to the primary domain.
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