Back to Intelligence

Veradigm Patient Data Breach: Defending Healthcare Orgs Against Third-Party Vendor Compromise and The Gentlemen Ransomware

SA
Security Arsenal Team
September 9, 2026
10 min read

Veradigm, a major healthcare technology and data analytics company serving providers, payers, and life sciences organizations, has disclosed a data breach after a cybersecurity incident at one of its third-party vendors exposed patient personal data. The ransomware group known as The Gentlemen has publicly claimed responsibility for the attack, describing it as an encryption-based operation — a hallmark of modern double-extortion campaigns where data is stolen before systems are locked.

For healthcare security teams, this incident is not just another breach headline. It is a case study in the threat vector that now dominates healthcare compromise statistics: the trusted third party. When a vendor with legitimate access to PHI (Protected Health Information) is breached, your perimeter defenses, EDR stack, and MFA policies are largely irrelevant to the initial intrusion. The attacker inherits the trust you extended to that vendor — and HIPAA liability stays with you.

This post breaks down what we know about the Veradigm incident, the operational profile of The Gentlemen ransomware group, and — most importantly — the concrete detection, hunting, and hardening steps your SOC should implement this week.

What Happened

According to Veradigm's disclosure, a cybersecurity incident at a third-party vendor resulted in unauthorized access to patient personal data. The Gentlemen ransomware gang claimed the attack on its leak site, consistent with the group's established pattern of naming victims and threatening data publication to force payment.

Key characteristics of this incident pattern:

  • Initial access via a vendor, not Veradigm's core environment directly. This shifts the kill chain outside the victim's monitored estate.
  • Encryption-based attack, per the gang's own description — indicating ransomware deployment, likely preceded by data exfiltration for double extortion.
  • PHI exposure, triggering HIPAA Breach Notification Rule obligations (45 CFR §§ 164.400-414), including individual notification within 60 days of discovery, HHS reporting, and media notification for breaches affecting 500+ individuals in a state.

This follows a well-documented 2024–2026 trend in which healthcare business associates and their downstream vendors — EHR integrators, billing platforms, data analytics firms, managed IT providers — serve as the intrusion path into covered entities. The Change Healthcare and Ascension incidents demonstrated the systemic blast radius; Veradigm is the latest confirmation that adversaries have operationalized this model.

The Gentlemen: Threat Actor Profile

The Gentlemen is a ransomware-as-a-service (RaaS) operation that emerged in 2025 and quickly built one of the more active victim lists among mid-tier ransomware crews. Defenders should understand their tradecraft:

  • Double extortion as standard: Exfiltration precedes encryption. Even if you restore from backups, the leak threat remains. Assume any ransomware claim includes data theft until forensically disproven.
  • Living-off-the-land tooling: Observed operations use native Windows utilities — vssadmin, wbadmin, bcdedit — to destroy recovery options before encryption, reducing the malware signature footprint.
  • RDP and VPN edge access: Initial access frequently traces to exposed remote access services, compromised credentials, or — as in this case — trusted third-party connections.
  • Fast encryption timelines: Modern crews compress dwell time. From hands-on-keyboard to mass encryption can be hours, not weeks, once the objective network is mapped.

Detection & Response

The detections below target the observable behaviors that define this threat class: shadow copy destruction, mass file encryption, anomalous third-party/vendor account activity, and bulk data staging. They are written to be high-fidelity — deploy them, tune the vendor-account scopes to your environment, and validate against your baseline.

Sigma Rules

YAML
---
title: Shadow Copy Deletion via Native Windows Utilities
description: Detects deletion of volume shadow copies using vssadmin, wmic, or PowerShell — a near-universal precursor to ransomware encryption observed in The Gentlemen and peer operations.
references:
  - https://attack.mitre.org/techniques/T1490/
  - https://www.bleepingcomputer.com/news/security/veradigm-discloses-patient-data-breach-after-gentlemen-gang-claims-attack/
author: Security Arsenal
id: 3f8c2a71-9b4d-4e62-a1c8-7d5e9f0b2a34
status: experimental
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\vssadmin.exe'
      - '\wmic.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
  selection_cli:
    CommandLine|contains:
      - 'delete shadows'
      - 'shadowcopy delete'
      - 'resize shadowstorage'
      - 'Remove-WmiObject win32_shadowcopy'
      - 'Get-WmiObject Win32_Shadowcopy'
  condition: selection_img and selection_cli
falsepositives:
  - Rare. Backup administrators occasionally resize shadowstorage; deletion of all shadows is not legitimate routine activity.
level: high
---
title: Backup Catalog and Boot Configuration Tampering
description: Detects wbadmin catalog deletion and bcdedit recovery-disabling commands, used by ransomware operators to prevent system recovery before encryption.
references:
  - https://attack.mitre.org/techniques/T1490/
  - https://attack.mitre.org/techniques/T1562.001/
author: Security Arsenal
id: 8a1d4e96-2c7f-4b38-9d51-3e6a0f4c8b17
status: experimental
logsource:
  category: process_creation
  product: windows
detection:
  selection_wbadmin:
    Image|endswith: '\wbadmin.exe'
    CommandLine|contains:
      - 'delete catalog'
      - 'delete systemstatebackup'
  selection_bcdedit:
    Image|endswith: '\bcdedit.exe'
    CommandLine|contains:
      - 'recoveryenabled no'
      - 'bootstatuspolicy ignoreallfailures'
  condition: 1 of selection_*
falsepositives:
  - Some imaging/provisioning tools modify boot configuration. Correlate with other ransomware precursors before dismissing.
level: high
---
title: Mass File Renaming Indicative of Ransomware Encryption
description: Detects high-volume file rename operations by a single process within a short window — a behavioral indicator of active file encryption.
references:
  - https://attack.mitre.org/techniques/T1486/
author: Security Arsenal
id: 5c9e7b02-4a1d-4f83-b6e2-0d8c3a7f5e91
status: experimental
logsource:
  category: file_rename
  product: windows
detection:
  selection:
    TargetFilename|endswith:
      - '.encrypted'
      - '.locked'
      - '.crypted'
  condition: selection
falsepositives:
  - Legitimate encryption tools are uncommon on servers. Tune the extension list to confirmed gang extensions during an active incident; treat any hit as P1 pending triage.
level: critical

KQL Hunt — Microsoft Sentinel / Defender

This query hunts for the recovery-destruction tooling pattern across your estate, plus anomalous activity from accounts associated with third-party vendors — the exact vector in the Veradigm incident. Scope the vendor UPN/domain filters to your environment.

KQL — Microsoft Sentinel / Defender
// Hunt 1: Ransomware recovery-destruction tooling (vssadmin/wbadmin/bcdedit)
let recoveryTools = dynamic(["vssadmin.exe", "wbadmin.exe", "bcdedit.exe", "wmic.exe"]);
let destructiveArgs = dynamic(["delete shadows", "delete catalog", "recoveryenabled no", "ignoreallfailures", "shadowcopy delete"]);
union isfuzzy=true
    (DeviceProcessEvents
    | where TimeGenerated > ago(7d)
    | where FileName has_any (recoveryTools)
    | where ProcessCommandLine has_any (destructiveArgs)
    | project TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName),
    (SecurityEvent
    | where TimeGenerated > ago(7d)
    | where EventID == 4688
    | where Process has_any (recoveryTools)
    | where CommandLine has_any (destructiveArgs)
    | project TimeGenerated, DeviceName = Computer, AccountName = Account, FileName = Process, ProcessCommandLine = CommandLine, InitiatingProcessFileName = ParentProcessName);

// Hunt 2: Anomalous activity from third-party vendor accounts
// Replace vendor domain/UPN suffixes with your actual vendor account naming conventions
let vendorAccounts = dynamic(["@vendor", "-svc-", "_ext", "@partner"]);
SigninLogs
| where TimeGenerated > ago(14d)
| where UserPrincipalName has_any (vendorAccounts)
| where ResultType != 0 or IPAddress !in (dynamic([]))  // failed logons OR unexpected IPs
| summarize FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated),
            Locations=make_set(Location), IPs=make_set(IPAddress),
            Apps=make_set(AppDisplayName), Attempts=count()
    by UserPrincipalName
| where array_length(IPs) > 3 or Attempts > 50
| order by Attempts desc;

// Hunt 3: Bulk file access on PHI repositories (data staging for exfiltration)
DeviceFileEvents
| where TimeGenerated > ago(24h)
| where ActionType in ("FileCreated", "FileModified")
| where FolderPath has_any ("\\ehr\\", "\\phi\\", "\\patient", "\\backup\\", "\\shares\\")
| summarize FileOps=count(), DistinctPaths=dcount(FolderPath)
    by DeviceName, InitiatingProcessAccountName, bin(TimeGenerated, 15m)
| where FileOps > 500
| order by FileOps desc;

Velociraptor VQL — Endpoint Forensics

Use this artifact during scoping to identify encryption precursors and suspicious process execution on servers hosting or adjacent to PHI data stores — particularly vendor-managed jump boxes and integration servers.

VQL — Velociraptor
-- Hunt for ransomware precursor activity: recovery-tool execution,
-- suspicious processes running from temp/appdata, and shadow copy state
SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(delete shadows|delete catalog|recoveryenabled no|shadowcopy)'
   OR Exe =~ '(?i)(\\temp\\|\\appdata\\|\\programdata\\|\\users\\public\\)[^\\]+\.exe$'

// Cross-reference: verify shadow copies still exist on the host
SELECT * FROM execve(argv=['powershell.exe', '-Command',
   'Get-WmiObject Win32_ShadowCopy | Select-Object DeviceObject, InstallDate'])

Remediation & Verification Script

Run this on Windows servers and vendor-accessible systems to verify recovery posture, audit for recovery-tampering events, and confirm shadow copies are intact.

PowerShell
# ============================================================
# Ransomware Recovery Posture & Tampering Audit - Security Arsenal
# Run elevated on PHI-adjacent servers and vendor jump boxes
# ============================================================

# 1. Verify shadow copies exist and report last creation time
Write-Host "[*] Checking Volume Shadow Copy state..." -ForegroundColor Cyan
$shadows = Get-CimInstance Win32_ShadowCopy -ErrorAction SilentlyContinue
if ($shadows) {
    $shadows | Select-Object DeviceObject, InstallDate | Format-Table -AutoSize
} else {
    Write-Host "[!] WARNING: No shadow copies found. Verify backup coverage." -ForegroundColor Red
}

# 2. Confirm System Protection is enabled on all fixed volumes
Write-Host "[*] Checking System Protection status per volume..." -ForegroundColor Cyan
Get-CimInstance Win32_Volume | Where-Object { $_.DriveLetter } | ForEach-Object {
    $vol = $_.DriveLetter
    try {
        $status = (Get-ComputerRestorePoint -ErrorAction Stop | Out-Null; "Queryable")
    } catch { $status = "Unknown/Disabled" }
    Write-Host "    $vol - Restore point status: $status"
}
vssadmin list shadowstorage

# 3. Audit recent use of recovery-destruction commands (last 7 days)
Write-Host "[*] Auditing process creation events for destructive tooling..." -ForegroundColor Cyan
$start = (Get-Date).AddDays(-7)
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4688; StartTime=$start} -ErrorAction SilentlyContinue |
    Where-Object { $_.Message -match 'delete shadows|delete catalog|recoveryenabled no|shadowcopy delete|ignoreallfailures' } |
    Select-Object TimeCreated, Message | Format-List

# 4. Audit local admins and recently added accounts (vendor persistence check)
Write-Host "[*] Enumerating local administrators for unexpected vendor accounts..." -ForegroundColor Cyan
Get-LocalGroupMember -Group 'Administrators' -ErrorAction SilentlyContinue |
    Select-Object Name, ObjectClass, PrincipalSource | Format-Table -AutoSize

Write-Host "[*] Accounts created in the last 30 days..." -ForegroundColor Cyan
Get-LocalUser | Where-Object { $_.PasswordLastSet -gt (Get-Date).AddDays(-30) } |
    Select-Object Name, Enabled, LastLogon, PasswordLastSet | Format-Table -AutoSize

# 5. Verify SMBv1 disabled (legacy lateral-movement surface)
Write-Host "[*] SMBv1 status:" -ForegroundColor Cyan
Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -ErrorAction SilentlyContinue |
    Select-Object FeatureName, State

Remediation and Third-Party Risk Hardening

The Veradigm incident is a third-party risk management failure as much as a technical one. Concrete actions for healthcare security and vendor-risk teams:

Immediate (this week):

  1. Inventory vendor access paths. Enumerate every third party with network access, API keys, service accounts, or data feeds touching PHI. You cannot defend trust relationships you have not mapped. Cross-reference against your Business Associate Agreement (BAA) register.
  2. Enforce least privilege on vendor accounts. Vendor service accounts should be scoped to specific systems, time-bound (JIT access where possible), and MFA-protected with phishing-resistant methods. Disable standing VPN access in favor of brokered, session-recorded remote access.
  3. Verify your backup integrity and isolation. Test restores from immutable/offline backups. Confirm shadow copies and backup catalogs are monitored for deletion — see the detections above.
  4. Contract review. Confirm BAAs include breach notification SLAs (24–72 hours to you, so you can meet your own 60-day HIPAA clock), right-to-audit clauses, and minimum security control requirements aligned to NIST CSF 2.0 and HICP (Health Industry Cybersecurity Practices).

Short term (30 days):

  1. Segment vendor-facing systems. Vendor integration servers, SFTP drops, and ETL pipelines should sit in dedicated segments with explicit egress filtering and no lateral path to clinical networks or EHR databases.
  2. Deploy the detection content above. Onboard the Sigma rules, validate the KQL hunts against your Sentinel workspace, and baseline vendor-account behavior so anomalies stand out.
  3. Tabletop the scenario. Run an exercise: your largest data vendor reports ransomware with your PHI on the encryption target. Walk the HIPAA notification timeline, legal hold, forensics scoping (whose IR team — yours or theirs?), and patient communication plan.

If you are a Veradigm customer or downstream of the affected vendor:

  1. Engage Veradigm's incident contact to determine whether your patient population is in scope, request forensic details on data categories exposed, and begin breach risk assessment under 45 CFR § 164.402 — the four-factor analysis (nature of PHI, unauthorized person, whether PHI was actually acquired/viewed, mitigation) determines notification obligations.
  2. Preserve logs and evidence now — authentication logs for vendor integrations, data transfer records, API access logs — before retention windows expire.

The Bottom Line

Encryption-based attacks on healthcare vendors are not an edge case anymore — they are the primary breach vector for PHI exposure in 2026. The adversary has learned that the path of least resistance into a covered entity runs through its least-defended business associate. Your detection strategy must extend to the trust boundary, your contracts must enforce security minimums, and your IR plan must assume the first call about a breach in your data comes from someone else's SOC.

Related Resources

Security Arsenal Healthcare Cybersecurity AlertMonitor Platform Book a SOC Assessment healthcare Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.