Back to Intelligence

Ransomware Surge in July: Detection and Hardening Guidance for Finance, Technology, and Healthcare Defenders

SA
Security Arsenal Team
August 8, 2026
11 min read

The brief reprieve many security operations teams felt in Q2 is over. According to new tracking data from Comparitech, ransomware activity surged sharply in July, reversing the relative lull observed through the second quarter of the year. The concentration matters: finance, technology, and healthcare organizations absorbed a disproportionate share of the attack volume — the three sectors where downtime translates directly into financial loss, service disruption, or patient safety risk.

If you run a SOC in any of these verticals, treat this as an operational warning, not a news cycle blip. Surges of this nature historically track with affiliate regrouping after takedowns, the onboarding of new initial access broker (IAB) inventory, and the seasonal exploitation of summer staffing gaps in incident response coverage. The correct response is to validate your detection posture against the behaviors ransomware operators execute in every successful intrusion — before the encryption stage, because by then you've already lost.

This post breaks down what the surge means for defenders, maps the attack chain you should be hunting against, and provides deployable Sigma, KQL, and Velociraptor content plus a hardening script.

Technical Analysis: The Attack Chain Behind the Surge

What the data tells us

Comparitech's tracking indicates July's volume represents a clear inflection from Q2 baselines, with finance, technology, and healthcare organizations particularly heavily targeted. Sector concentration of this kind is rarely random. These verticals share three characteristics that make them attractive to ransomware-as-a-service (RaaS) affiliates:

  • Pressure to pay: Healthcare and financial services face regulatory and human-safety consequences from extended outages, shortening the victim's decision timeline.
  • Data exfiltration leverage: All three sectors hold regulated, high-value data (PHI, PII, financial records) that strengthens double-extortion demands.
  • Large, heterogeneous attack surfaces: Technology companies and hospital networks run sprawling estates with legacy systems, third-party integrations, and internet-facing remote access infrastructure — the initial access points affiliates consistently exploit.

The intrusion lifecycle you must detect

No CVE is associated with this reporting — the surge is driven by technique, not a single vulnerability. Modern ransomware intrusions follow a remarkably consistent chain, and every stage is observable:

  1. Initial access — Phishing with credential harvesting, exploitation of internet-facing VPN/remote access appliances, or purchased access from IABs via RDP and VPN credentials.
  2. Execution and defense evasion — Hands-on-keyboard operators living off the land: PowerShell, WMI, PsExec, and abuse of legitimate remote management tooling.
  3. Discovery and lateral movement — Network scanning, enumeration of domain controllers and backup infrastructure, movement over SMB/RDP/WinRM.
  4. Impact preparation — The critical pre-encryption window: shadow copy deletion (vssadmin delete shadows, wmic shadowcopy delete), backup catalog tampering, boot configuration changes (bcdedit), and disabling of recovery options.
  5. Encryption and exfiltration — Mass file modification with entropy spike, ransom note deployment (commonly README, DECRYPT, RECOVER, or HOW_TO_DECRYPT filenames), and data staging to exfiltration endpoints.

The defender's advantage is that stages 1–4 unfold over hours to weeks. The encryption stage is loud but late. Your detection investment belongs in the pre-impact behaviors.

Exploitation status

This is confirmed, active, in-the-wild criminal activity at elevated volume — not theoretical risk. There is no single CVE to patch; the defensive requirement is behavioral detection, credential hygiene, and hardening of remote access and backup infrastructure.

Detection & Response

The following detection content targets the pre-encryption behaviors common to the ransomware intrusions driving this surge. Each rule is designed for high-fidelity signal in enterprise environments — but as always, baseline against your administrative tooling before pushing to production.

Sigma Rules

YAML
---
title: Shadow Copy Deletion via Command Line - Ransomware Impact Preparation
id: 8f2c4a11-7b3d-4e5f-9a01-2c6d8e4f5a7b
status: experimental
description: Detects deletion of volume shadow copies via vssadmin, wmic, or PowerShell, a hallmark pre-encryption behavior in ransomware intrusions targeting finance, technology, and healthcare organizations.
references:
  - https://attack.mitre.org/techniques/T1490/
  - https://www.infosecurity-magazine.com/news/ransomware-surges-july-q2-lull/
author: Security Arsenal
date: 2026/01/15
tags:
  - attack.impact
  - attack.t1490
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'
      - 'DeleteShadows'
      - 'Win32_ShadowCopy'
  condition: selection_img and selection_cli
falsepositives:
  - Legitimate backup maintenance scripts (rare; validate against change windows)
  - System administrators performing storage reclamation
level: high
---
title: Boot Configuration and Recovery Options Tampering via bcdedit
id: 3d9e7b22-1c4f-4a6e-8b02-5d7c9f3a6b8c
status: experimental
description: Detects bcdedit modifications disabling recovery mode or ignoring boot failures, a technique used by ransomware operators to prevent system recovery during encryption events.
references:
  - https://attack.mitre.org/techniques/T1490/
  - https://www.infosecurity-magazine.com/news/ransomware-surges-july-q2-lull/
author: Security Arsenal
date: 2026/01/15
tags:
  - attack.impact
  - attack.t1490
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith: '\bcdedit.exe'
  selection_cli:
    CommandLine|contains:
      - 'recoveryenabled no'
      - 'bootstatuspolicy ignoreallfailures'
  condition: selection_img and selection_cli
falsepositives:
  - Rare; some imaging or kiosk hardening scripts modify boot policy
level: high
---
title: Ransomware Note Artifact Creation in User Directories
id: 6b1a8d33-9e5c-4f7d-ac13-8e4d0a2b7c9d
status: experimental
description: Detects creation of files matching common ransomware note naming patterns across user and public directories, indicating an active or completed encryption event.
references:
  - https://attack.mitre.org/techniques/T1486/
  - https://www.infosecurity-magazine.com/news/ransomware-surges-july-q2-lull/
author: Security Arsenal
date: 2026/01/15
tags:
  - attack.impact
  - attack.t1486
logsource:
  category: file_event
  product: windows
detection:
  selection:
    TargetFilename|contains:
      - 'DECRYPT'
      - 'HOW_TO_DECRYPT'
      - 'RECOVER_FILES'
      - 'RESTORE_FILES'
      - 'README_FOR_DECRYPT'
      - 'READ_ME_TO_RECOVER'
    TargetFilename|endswith:
      - '.txt'
      - '.hta'
      - '.html'
  condition: selection
falsepositives:
  - Security tooling or canary files intentionally named to lure ransomware
  - Rare legitimate documentation files (tune allowlist per environment)
level: critical

KQL — Microsoft Sentinel / Defender

KQL — Microsoft Sentinel / Defender
// Hunt: Pre-encryption ransomware preparation behaviors
// Targets shadow copy deletion, boot tampering, and backup service disruption
// across the estate over a 7-day window.
let lookback = 7d;
let suspiciousCmds = dynamic([
  "delete shadows", "shadowcopy delete", "DeleteShadows",
  "Win32_ShadowCopy", "recoveryenabled no",
  "bootstatuspolicy ignoreallfailures", "wbadmin delete catalog",
  "wbadmin delete systemstatebackup"
]);
union isfuzzy=true
  (DeviceProcessEvents
  | where Timestamp > ago(lookback)
  | where FileName in~ ("vssadmin.exe", "wmic.exe", "bcdedit.exe", "wbadmin.exe", "powershell.exe", "pwsh.exe")
  | where ProcessCommandLine has_any (suspiciousCmds)
  | project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessAccountName, ReportId),
  (SecurityEvent
  | where TimeGenerated > ago(lookback)
  | where EventID == 4688
  | where NewProcessName has_any ("vssadmin.exe", "wmic.exe", "bcdedit.exe", "wbadmin.exe", "powershell.exe")
  | where CommandLine has_any (suspiciousCmds)
  | project TimeGenerated, Computer, Account, NewProcessName, CommandLine, ParentProcessName)
| sort by Timestamp desc

A companion hunt for mass file modification — the encryption event itself — is worth running as an analytic rule with a high aggregation threshold, so routine user activity doesn't trip it:

KQL — Microsoft Sentinel / Defender
// Hunt: Mass file rename/modification indicative of active encryption
// Flags single devices with abnormally high file operation volume in short windows.
DeviceFileEvents
| where Timestamp > ago(1d)
| where ActionType in ("FileRenamed", "FileModified")
| where InitiatingProcessFileName !in~ ("explorer.exe", "onedrive.exe", "searchprotocolhost.exe", "searchindexer.exe", "svchost.exe")
| summarize FileOps = count(), DistinctExtensions = dcount(tostring(split(FileName, ".")[-1])), FirstSeen = min(Timestamp), LastSeen = max(Timestamp)
    by DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, bin(Timestamp, 10m)
| where FileOps > 500 and DistinctExtensions > 10
| extend DurationSeconds = datetime_diff("second", LastSeen, FirstSeen)
| sort by FileOps desc

Tune the FileOps > 500 threshold against your environment — software build servers and backup agents are the usual noise sources. The DistinctExtensions > 10 condition is doing real work: legitimate bulk operations are usually homogeneous, while encryption touches everything.

Velociraptor VQL

For DFIR responders validating a suspected intrusion, this artifact pulls process execution matching ransomware preparation patterns alongside ransom note artifacts on disk:

VQL — Velociraptor
-- Hunt artifact: Ransomware preparation and impact indicators
-- Stage 1: Process execution matching pre-encryption behaviors
LET proc_hits = SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(delete shadows|shadowcopy delete|recoveryenabled no|bootstatuspolicy ignoreallfailures|wbadmin delete|bcdedit)'

-- Stage 2: Ransom note artifacts across user profiles
LET note_hits = SELECT FullPath, Size, Mtime, Btime
FROM glob(globs=[
  'C:/Users/*/Desktop/*DECRYPT*',
  'C:/Users/*/Documents/*DECRYPT*',
  'C:/Users/*/Desktop/*RECOVER*',
  'C:/Users/*/Desktop/*README*',
  'C:/Users/Public/**/*DECRYPT*'
])
WHERE Size < 1048576

SELECT 'Process' AS IndicatorType, CommandLine AS Indicator, Username AS Context, CreateTime AS Timestamp FROM proc_hits
UNION ALL
SELECT 'RansomNote' AS IndicatorType, FullPath AS Indicator, format(format='%d bytes', args=Size) AS Context, Mtime AS Timestamp FROM note_hits
ORDER BY Timestamp DESC

Deploy this as a hunt scoped to endpoint groups in your highest-risk segments — clinical workstations, financial operations systems, and anything reachable from internet-facing access infrastructure.

Remediation Script — PowerShell

PowerShell
# Ransomware resilience audit and hardening script
# Run elevated on Windows endpoints and servers. Read-only audit by default;
# pass -Remediate to apply hardening changes.

param([switch]$Remediate)

Write-Host "=== Ransomware Resilience Audit ===" -ForegroundColor Cyan

# 1. Verify VSS service is not disabled and shadow copies exist
$vss = Get-Service -Name VSS -ErrorAction SilentlyContinue
Write-Host "[1] VSS Service Status: $($vss.Status) / StartType: $($vss.StartType)"
$shadows = Get-CimInstance Win32_ShadowCopy -ErrorAction SilentlyContinue
Write-Host "    Shadow copies present: $($shadows.Count)"
if ($Remediate -and $vss.StartType -eq 'Disabled') {
    Set-Service -Name VSS -StartupType Manual
    Write-Host "    REMEDIATED: VSS service re-enabled (Manual)" -ForegroundColor Yellow
}

# 2. Check controlled folder access (ransomware protection) state
$asr = Get-MpPreference -ErrorAction SilentlyContinue
$cfa = $asr.EnableControlledFolderAccess
Write-Host "[2] Controlled Folder Access state: $cfa (1=Enabled, 2=Audit, 0=Disabled)"
if ($Remediate -and $cfa -ne 1) {
    Set-MpPreference -EnableControlledFolderAccess Enabled
    Write-Host "    REMEDIATED: Controlled Folder Access enabled" -ForegroundColor Yellow
    Write-Host "    NOTE: Add LOB application exclusions to avoid breakage" -ForegroundColor Yellow
}

# 3. Verify attack surface reduction rules for common ransomware vectors
$asrRules = @{
    '56a863a9-875e-4185-98a7-b882c64b5ce5' = 'Block abuse of exploited vulnerable signed drivers'
    '7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c' = 'Block Adobe Reader child processes'
    'be9ba2d9-53ea-4cdc-84e5-9b1eeee46550' = 'Block executable content from email/webmail'
    'd4f940ab-401b-4efc-aadc-ad5f3c50688a' = 'Block Office apps from creating child processes'
    'c1db55ab-c21a-4637-bb3f-a12568109d35' = 'Use advanced ransomware protection'
}
Write-Host "[3] ASR Rule Status:"
foreach ($rule in $asrRules.GetEnumerator()) {
    $idx = [array]::IndexOf($asr.AttackSurfaceReductionRules_Ids, $rule.Key)
    $state = if ($idx -ge 0) { $asr.AttackSurfaceReductionRules_Actions[$idx] } else { 'Not configured' }
    Write-Host "    $($rule.Value): $state (0=Off, 1=Block, 2=Audit)"
}

# 4. Audit for exposed SMBv1 and unsigned/RDP risk
$smb1 = Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -ErrorAction SilentlyContinue
Write-Host "[4] SMBv1 state: $($smb1.State) (should be Disabled)"
if ($Remediate -and $smb1.State -eq 'Enabled') {
    Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart
    Write-Host "    REMEDIATED: SMBv1 disabled (restart required)" -ForegroundColor Yellow
}

# 5. Flag recent shadow deletion events in the last 72 hours
$cutoff = (Get-Date).AddHours(-72)
$vssEvents = Get-WinEvent -FilterHashtable @{LogName='System'; Id=7036,7040; StartTime=$cutoff} -ErrorAction SilentlyContinue |
    Where-Object { $_.Message -match 'Volume Shadow Copy' }
Write-Host "[5] VSS service state changes (72h): $($vssEvents.Count)"
if ($vssEvents) { Write-Host "    WARNING: Investigate VSS service manipulation" -ForegroundColor Red }

Write-Host "=== Audit Complete ===" -ForegroundColor Cyan

Run the audit mode across your estate first. Enable -Remediate only after validating that Controlled Folder Access won't break line-of-business applications — in healthcare especially, test against clinical applications and EHR clients in a pilot ring before broad enforcement.

Remediation and Defensive Priorities

Because this surge is technique-driven rather than vulnerability-driven, there is no single patch to deploy. The remediation program is a prioritized hardening sequence. Work it in order:

  1. Lock down initial access vectors (days 1–7).

    • Enforce phishing-resistant MFA (FIDO2/passkeys) on all remote access — VPN, RDP gateways, VDI, and cloud identity. Credential-only remote access is the single most common entry point in these intrusions.
    • Inventory every internet-facing appliance and confirm patch currency. Subscribe to vendor advisories for your VPN, firewall, and remote access stack; these appliances are the highest-frequency exploitation targets for initial access.
    • Disable SMBv1 everywhere. Audit for exposed RDP (TCP 3389) reachable from the internet — there should be none.
  2. Deploy and tune the detections above (days 1–14).

    • Push the Sigma rules through your pipeline, deploy the KQL as scheduled analytics, and scope the VQL hunt to high-risk segments.
    • Establish a baseline now, while volume is elevated: any shadow copy deletion outside a documented change window is a page-the-on-call event.
  3. Protect the recovery path (days 7–30).

    • Implement immutable or air-gapped backups with a credential boundary between production and backup infrastructure. Operators explicitly hunt backup catalogs (wbadmin delete catalog) before encrypting — if your backups share domain trust with production, they will be destroyed.
    • Test restoration. An untested backup is a hypothesis, not a control. Time the restore of a critical system; in healthcare, that number belongs in your downtime procedures.
  4. Exercise the response (before you need it).

    • Run a tabletop against the surge scenario: encryption event in a clinical or financial operations segment during reduced staffing hours. Validate decision authority for isolation, the out-of-band communication tree, and whether your IR retainer's SLA matches the current threat tempo.
  5. Report and engage.

    • U.S. organizations: report incidents to CISA (report@cisa.gov) and FBI IC3. Healthcare entities must also evaluate HIPAA breach notification obligations where PHI exfiltration is confirmed; financial institutions should review sector-specific notification requirements (GLBA, state regulators, and for covered entities, SEC or banking regulator timelines).

The Q2 lull was a regrouping, not a retreat. July's numbers say the affiliates are back and they know which sectors feel pain fastest. The organizations that absorb this surge without paying will be the ones that catch the intrusion at stage 3 or 4 — not stage 5.

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.