Back to Intelligence

Ransomware Threat Intelligence: How Defenders Track Adversary Infrastructure and Stop Encryption Attacks Before Detonation

SA
Security Arsenal Team
September 25, 2026
11 min read

The most expensive sentence in incident response is the one your SOC never got to write: "We saw this coming." Recorded Future's latest guidance on encryption-based cyber incident threat intelligence makes a point I've been hammering into clients for years — ransomware is not a zero-warning event. Long before the encryptor executes, the adversary has registered infrastructure, purchased initial access from a broker, tested payloads against your EDR vendor's trial builds, and possibly discussed your organization by name in a closed Telegram channel or dark web forum. Every one of those steps generates observable, collectible intelligence.

Ransomware remains the single highest-impact threat class my team responds to. Median dwell time has compressed to days — sometimes hours — which means detection-at-execution is a losing strategy. The organizations that consistently avoid paying ransoms are the ones that operationalize threat intelligence: tracking ransomware-as-a-service (RaaS) infrastructure, monitoring initial access broker (IAB) listings, watching leak sites for pre-attack chatter, and feeding all of it into detection engineering. This post breaks down how to build that capability, with the detection content your SOC can deploy today.

Technical Analysis: The Ransomware Kill Chain and Where Intelligence Intercepts It

Modern ransomware operations — whether operated by established RaaS brands or the splinter groups and rebrand crews that filled the vacuum left by 2024–2025 law enforcement takedowns — follow a predictable, intelligence-rich lifecycle:

1. Initial access acquisition. IABs sell validated access on dark web marketplaces: RDP credentials, VPN credentials harvested by infostealers, webshells on unpatched edge devices, and access brokered from phishing campaigns. Listings frequently include victim industry, revenue, and geography — sometimes enough to identify your organization before you're attacked. Infostealer log markets (Russian Market-style shops and Telegram bot channels) are a top source of corporate credentials that later become ransomware intrusions.

2. Infrastructure staging. Affiliates register C2 domains, stand up Cobalt Strike or Sliver team servers, and provision bulletproof hosting. These artifacts are trackable: TLS certificate patterns, JA3/JA4 fingerprints, nameserver clustering, and domain registration cadence are all high-fidelity pivots. Threat intel platforms automate exactly this tracking.

3. Intrusion and preparation. Hands-on-keyboard activity: disabling backups (vssadmin delete shadows, bcdedit tampering), killing security tooling (BYOVD drivers, EDR tampering), staging data exfiltration to MEGA/Rclone/cloud endpoints, and deploying PsExec or Group Policy for lateral spread.

4. Encryption and extortion. Mass file modification with a consistent extension, ransom note drops, and — increasingly common in 2025–2026 — exfil-only extortion without encryption at all.

The defensive implication: stages 1–3 are where you win. Stage 4 is where you lose. Intelligence on stages 1–2 gives you days of warning; behavioral detection on stage 3 gives you minutes to hours; detection on stage 4 gives you a postmortem.

Exploitation Status

This is not a theoretical threat. Ransomware crews actively exploited edge-device vulnerabilities throughout 2025 (multiple entries in CISA's Known Exploited Vulnerabilities catalog were weaponized by ransomware affiliates within days of disclosure), and infostealer-driven credential access remains the dominant initial vector in the engagements we respond to. Dark web chatter correlating specific victims to subsequent attacks is a documented, repeatable pattern — Recorded Future and peer vendors routinely surface IAB listings that precede public ransomware disclosures.

Operationalizing Threat Intelligence: What Actually Works

From the trenches, here's the intelligence workflow that produces defensive outcomes rather than dashboard decoration:

  • Monitor IAB marketplaces and infostealer channels for your domains, subsidiaries, and key suppliers. Alert on any credential or access listing touching your estate. Force-rotate exposed credentials within hours, not at next quarter's password cycle.
  • Track RaaS infrastructure feeds. Ingest curated feeds of C2 domains/IPs for Cobalt Strike, Sliver, Brute Ratel, and ransomware tooling into your firewall, proxy, and EDR block lists. Intelligence without enforcement is trivia.
  • Watch leak sites and Telegram for brand mentions. Victim-shaming posts about competitors in your vertical are leading indicators — crews work sector by sector when a new access vector pays off.
  • Map intelligence to detection. Every reported TTP should answer: do we have a detection for this, and did it fire in a purple-team test? Intel-to-detection traceability is the difference between a TI program and a news subscription.

Detection & Response

The detections below target the highest-signal pre-encryption behaviors common across ransomware families. These are the behaviors that matter regardless of which crew or variant shows up — which is exactly what intelligence-driven defense is supposed to abstract away.

Sigma Rules

YAML
---
title: Ransomware Shadow Copy Deletion via vssadmin wmic or PowerShell
id: 3f9c1a72-8b2d-4e61-a5c4-7d8e9f0a1b2c
status: experimental
description: Detects deletion or resizing of volume shadow copies, a near-universal ransomware precursor behavior used to destroy recovery options before encryption.
references:
  - https://attack.mitre.org/techniques/T1490/
  - https://www.recordedfuture.com/blog/ransomware-threat-intelligence
author: Security Arsenal
date: 2026/04/06
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'
      - 'delete shadow'
      - 'resize shadowstorage'
      - 'Remove-WmiObject win32_shadowcopy'
  condition: all of selection_*
falsepositives:
  - Backup administrators performing storage maintenance
  - Legitimate VSS troubleshooting
level: high
---
title: Ransomware Boot Recovery and Backup Service Tampering
id: 8c2e5b41-6f3a-4d79-b1e8-2a4c6d8f0e1a
status: experimental
description: Detects bcdedit recovery tampering and mass stopping of backup/database services, consistent with ransomware pre-encryption staging observed across RaaS affiliates.
references:
  - https://attack.mitre.org/techniques/T1490/
  - https://attack.mitre.org/techniques/T1489/
  - https://www.recordedfuture.com/blog/ransomware-threat-intelligence
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1490
  - attack.t1489
logsource:
  category: process_creation
  product: windows
detection:
  selection_bcd:
    Image|endswith: '\bcdedit.exe'
    CommandLine|contains:
      - 'recoveryenabled no'
      - 'bootstatuspolicy ignoreallfailures'
  selection_net:
    Image|endswith:
      - '\net.exe'
      - '\net1.exe'
      - '\sc.exe'
    CommandLine|contains:
      - 'stop'
      - 'disable'
    CommandLine|contains:
      - 'veeam'
      - 'backup'
      - 'vss'
      - 'sql'
      - 'mssql'
      - 'exchange'
      - 'sophos'
  condition: selection_bcd or selection_net
falsepositives:
  - System administrators modifying boot configuration
  - Scheduled backup maintenance windows
level: high
---
title: Rclone or Cloud Sync Tool Execution from Non-Standard Path
id: 5d7a3f19-2e8c-4b45-9a1d-6c3e8f2b4a7d
status: experimental
description: Detects execution of rclone or similar exfiltration tooling from user-writable or temp paths, a common ransomware double-extortion staging behavior for data theft before encryption.
references:
  - https://attack.mitre.org/techniques/T1567.002/
  - https://www.recordedfuture.com/blog/ransomware-threat-intelligence
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.exfiltration
  - attack.t1567.002
logsource:
  category: process_creation
  product: windows
detection:
  selection_tool:
    - Image|endswith:
        - '\rclone.exe'
        - '\megacmd.exe'
        - '\winscp.com'
        - '\winscp.exe'
    - OriginalFileName:
        - 'rclone.exe'
  selection_path:
    Image|contains:
      - '\AppData\'
      - '\Temp\'
      - '\ProgramData\'
      - '\Users\Public\'
  condition: all of selection_*
falsepositives:
  - IT teams using rclone for legitimate cloud migration (whitelist approved paths)
level: medium

KQL — Microsoft Sentinel / Defender

This query hunts for the compound pre-encryption sequence — shadow copy deletion followed by mass file modification from the same process — plus credential-theft tooling indicators that threat intel feeds frequently tie to ransomware staging. Run it over a 7-day lookback for hunting, or adapt to a near-real-time analytics rule.

KQL — Microsoft Sentinel / Defender
// Hunt: Ransomware pre-encryption staging behaviors across the estate
let lookback = 7d;
let shadowKill = DeviceProcessEvents
    | where TimeGenerated > ago(lookback)
    | where (FileName =~ "vssadmin.exe" and ProcessCommandLine has_any ("delete shadows", "resize shadowstorage"))
        or (FileName =~ "wmic.exe" and ProcessCommandLine has "shadowcopy delete")
        or (FileName in~ ("powershell.exe", "pwsh.exe") and ProcessCommandLine has_any ("win32_shadowcopy", "delete shadows"))
        or (FileName =~ "bcdedit.exe" and ProcessCommandLine has_any ("recoveryenabled no", "ignoreallfailures"))
    | project ShadowKillTime=TimeGenerated, DeviceName, AccountName, InitiatingProcessFileName, FileName, ProcessCommandLine;
let massRename = DeviceFileEvents
    | where TimeGenerated > ago(lookback)
    | where ActionType == "FileRenamed"
    | summarize RenameCount=count(), DistinctExtensions=dcount(tostring(split(FileName, ".")[-1])), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated)
        by DeviceName, InitiatingProcessFileName, InitiatingProcessAccountName, bin(TimeGenerated, 5m)
    | where RenameCount > 100 and DistinctExtensions > 10;
shadowKill
| join kind=inner massRename on DeviceName
| where FirstSeen > ShadowKillTime
| project ShadowKillTime, FirstSeen, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, RenameCount, DistinctExtensions
| order by ShadowKillTime asc

A companion query for the intelligence-driven side — correlating network egress against newly observed ransomware C2 infrastructure ingested via your TI connector (the ThreatIntelligenceIndicator table in Sentinel):

KQL — Microsoft Sentinel / Defender
// Correlate outbound connections against ingested ransomware C2 threat intelligence
let lookback = 14d;
let ransomwareIOC = ThreatIntelligenceIndicator
    | where TimeGenerated > ago(lookback)
    | where isnotempty(NetworkIP) or isnotempty(NetworkDestinationIP) or isnotempty(DomainName)
    | where Description has_any ("ransomware", "cobalt", "sliver", "brute ratel", "lockbit", "blackcat", "akira", "play")
        or ThreatType has "c2"
    | extend IOC_IP = coalesce(NetworkIP, NetworkDestinationIP), IOC_Domain = DomainName;
DeviceNetworkEvents
| where TimeGenerated > ago(lookback)
| join kind=inner (ransomwareIOC | where isnotempty(IOC_IP) | project IOC_IP, Description) on $left.RemoteIP == $right.IOC_IP
| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, RemoteIP, RemotePort, Description
| order by TimeGenerated desc

Velociraptor VQL

For IR triage or proactive hunting, this artifact surfaces processes performing anti-recovery actions and enumerates recently dropped files resembling ransom notes across endpoints — useful when TI indicates a crew is active in your sector and you need to sweep for early footholds.

VQL — Velociraptor
-- Ransomware staging sweep: anti-recovery processes, suspicious execution paths, and ransom note artifacts
SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime,
       'Anti-Recovery Process' AS Indicator
FROM pslist()
WHERE CommandLine =~ '(?i)(delete shadows|shadowcopy delete|recoveryenabled no|ignoreallfailures|resize shadowstorage)'

UNION ALL

SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime,
       'LOLBIN from User-Writable Path' AS Indicator
FROM pslist()
WHERE Exe =~ '(?i)(appdata|temp|programdata|users\\\\public)'
  AND Name =~ '(?i)(rundll32|regsvr32|mshta|powershell|rclone|psexec)'

UNION ALL

SELECT 0 AS Pid, 0 AS Ppid, Name, FullPath AS CommandLine, FullPath AS Exe,
       'N/A' AS Username, Mtime AS CreateTime, 'Ransom Note Artifact' AS Indicator
FROM glob(globs=['C:/Users/*/Desktop/*READ*ME*.txt',
                 'C:/Users/*/Documents/*RECOVER*FILES*.txt',
                 'C:/Users/*/Desktop/*DECRYPT*.html',
                 'C:/ProgramData/*HOW*TO*RESTORE*.txt'])
WHERE Mtime > Now() - 604800

Remediation & Hardening Script

This PowerShell script verifies and enforces the control set that most directly blunts ransomware impact: protected shadow copies, attack surface reduction (ASR) rules targeting ransomware staging behaviors, and tamper protection. Run elevated; validate in audit mode before enforcing ASR blocks.

PowerShell
# Security Arsenal - Ransomware Pre-Encryption Hardening Verification
# Run as Administrator. Review ASR rules in Audit mode before switching to Block.

# 1. Verify VSS is operational and shadow copies exist (ransomware targets these first)
Write-Host "[+] Checking Volume Shadow Copy service and existing shadows..." -ForegroundColor Cyan
$vss = Get-Service VSS
if ($vss.StartType -eq 'Disabled') {
    Set-Service VSS -StartupType Manual
    Write-Warning "VSS was disabled - re-enabled to Manual (default). Investigate why it was disabled."
}
$shadows = Get-WmiObject Win32_ShadowCopy -ErrorAction SilentlyContinue
if (-not $shadows) {
    Write-Warning "No shadow copies present. Creating baseline restore point."
    Checkpoint-Computer -Description "Pre-Hardening Baseline" -RestorePointType "MODIFY_SETTINGS"
}

# 2. Verify Microsoft Defender Tamper Protection (ransomware crews attempt to disable it)
$tamper = Get-MpComputerStatus
if (-not $tamper.IsTamperProtected) {
    Write-Warning "Tamper Protection is OFF. Enable via Microsoft Defender portal: Security > Manage tamper protection."
}

# 3. Deploy key Attack Surface Reduction rules targeting ransomware TTPs (start in Audit mode)
$asrRules = @{
    'e6db77e5-3df2-4cf1-b95a-636979351e5b' = 'Block persistence via WMI event subscription'
    'd1e49aac-8f56-4280-b9ba-993a6d77406c' = 'Block process creations from PSExec/WMI'
    'b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4' = 'Block untrusted/unsigned processes from USB'
    '92e97fa1-2edf-4476-bdd6-9dd0b4dddc7b' = 'Block Win32 API calls from Office macros'
    'c1db55ab-c21a-4637-bb3f-a12568109d35' = 'Use advanced ransomware protection'
}
foreach ($rule in $asrRules.GetEnumerator()) {
    Set-MpPreference -AttackSurfaceReductionRules_Ids $rule.Key -AttackSurfaceReductionRules_Actions AuditMode
    Write-Host "[+] ASR rule set to Audit: $($rule.Value)" -ForegroundColor Green
}

# 4. Block common exfil/staging tooling by hash-agnostic path policy (AppLocker stub)
Write-Host "[+] Review AppLocker/WDAC policy for rclone.exe, megacmd.exe in user-writable paths." -ForegroundColor Cyan

# 5. Audit: flag any account not enrolled in MFA with VPN/RDP access (credential-based initial access)
Write-Host "[+] Verify MFA enforcement on all remote access - infostealer credentials remain the #1 ransomware entry vector." -ForegroundColor Cyan

Write-Host "[+] Complete. Re-run in 7-14 days and convert ASR rules from Audit to Block after tuning." -ForegroundColor Green

Remediation

There is no patch for ransomware — the fix is posture, visibility, and speed. Prioritized actions:

  1. Stand up dark web and IAB monitoring scoped to your estate. Alert on your domains, executive identities, subsidiaries, and critical suppliers appearing in access-broker listings or infostealer log channels. Establish a 4-hour SLA for force-rotating any exposed credential.
  2. Enforce phishing-resistant MFA on every remote access path — VPN, RDP gateways, VDI, SSO. Stolen credentials from infostealers are the dominant initial access vector; MFA is the single control that neutralizes most of them.
  3. Deploy and enforce the ASR rule set from the script above, moving from audit to block within two weeks. The "advanced ransomware protection" rule and the WMI/PsExec rules directly disrupt the staging phase.
  4. Isolate and immutably protect backups. Offline or object-lock/immutable copies, separate credentials, and quarterly restore tests. If vssadmin delete shadows succeeds in your environment, that is a detection gap, not just a hardening gap.
  5. Ingest ransomware C2 and infrastructure feeds into enforcement points — firewall egress, proxy, DNS filtering, and EDR network protection. Automate the pipeline so new indicators block within minutes, not after a weekly change review.
  6. Patch edge devices on an emergency cadence. Ransomware affiliates consistently weaponize newly disclosed VPN/firewall/hypervisor vulnerabilities within days. Subscribe to CISA KEV and treat KEV additions on internet-facing systems as 72-hour remediation deadlines.
  7. Test the detections above. Purple-team the shadow copy deletion, bcdedit tampering, and rclone staging behaviors quarterly. A Sigma rule that has never fired in a test is a hypothesis, not a control.

The bottom line: ransomware crews operate like businesses with marketing channels, supply chains, and infrastructure. Everything a business does is observable. Threat intelligence turns that observability into warning time — and warning time is the only currency that matters before the encryptor runs.

Related Resources

Security Arsenal Incident Response Services AlertMonitor Platform Book a SOC Assessment incident-response Intel Hub

Is your security operations ready?

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