Huntress recently documented a case that every SOC team should study: an Akira ransomware affiliate gained access to a victim environment, staged its encryption payload, and then attempted to blind the endpoint security stack before detonating. The anti-EDR effort backfired — the tampering destabilized the host and crashed the ransomware's own encryption routine, leaving the attack dead on arrival.
This is not a feel-good anecdote. It is operational proof of two things I have been telling clients for years: defense-in-depth works, and ransomware operators are not elite engineers. Affiliates in the Akira Ransomware-as-a-Service (RaaS) ecosystem are often mid-skill operators following playbooks they barely understand. When they reach for EDR-killer tooling — vulnerable drivers, tamper scripts, Defender exclusion abuse — they introduce fragility into their own attack chain.
But here is the sobering counterpoint: this affiliate got far enough to try. The EDR tampering attempt itself is a late-stage signal. If your detection coverage only lights up when the encryptor runs, you are one competent affiliate away from a bad weekend. This post breaks down the defensive lessons from the Huntress findings and gives you deployable detections for the EDR-evasion phase of the Akira intrusion lifecycle.
Technical Analysis: The Anti-EDR Phase of an Akira Intrusion
What Huntress Observed
Based on the Huntress reporting covered by Infosecurity Magazine, the affiliate's attack followed the now-standard Akira playbook:
- Initial access and staging — Akira affiliates historically gain entry via exposed VPN/remote access services (frequently targeting Cisco ASA/FTD VPNs without MFA), compromised credentials, or exploitation of public-facing applications. Once inside, they establish persistence and conduct discovery.
- Defense evasion attempt (MITRE ATT&CK T1562.001 — Impair Defenses: Disable or Modify Tools) — Before executing the encryptor, the operator attempted to neutralize endpoint detection and response tooling. This is the phase that failed. Modern anti-EDR tradecraft in the Akira ecosystem includes:
- BYOVD (Bring Your Own Vulnerable Driver, T1068 / T1562.001) — loading a legitimately signed but exploitable kernel driver to terminate security processes from ring 0. Akira operators have previously been observed deploying their own EDR-killer tooling built on abused signed drivers.
- Service and process termination — using
sc stop,sc delete,taskkill /f, ornet stopagainst security product services. - Registry-based Defender tampering — setting
DisableAntiSpywareorDisableRealtimeMonitoringunderHKLM\SOFTWARE\Microsoft\Windows Defenderor via policy keys. - PowerShell abuse of
Set-MpPreference— adding broad path/process exclusions or disabling real-time monitoring.
- Encryption failure — the tampering destabilized the system or the encryptor's execution context, and the Akira payload crashed mid-operation. The victim was left with a failed extortion attempt rather than a full encryption event.
Affected Products and Platforms
This is not a vulnerability story — no CVE is associated with this reporting, and I will not invent one. The affected surface is:
- Windows endpoints and servers running any EDR/AV stack the affiliate attempted to blind (the lesson applies regardless of vendor).
- Organizations with weak remote access hygiene — Akira continues to hammer VPN concentrators, RDP, and credential-reuse paths in 2025–2026 campaigns.
- Environments without kernel-level driver blocklisting (Microsoft's Vulnerable Driver Blocklist / WDAC) — these remain soft targets for BYOVD-style EDR killers.
Exploitation Status
This was a confirmed, real-world intrusion investigated by Huntress — not a theoretical technique. Akira remains one of the most active ransomware operations tracked by CISA and the FBI (see the joint CISA/FBI/EC3 advisory on Akira, AA24-109A, and its updates). EDR tampering is now a standard pre-encryption step across the ransomware ecosystem; the only thing unusual about this case is that it failed loudly.
The Defender's Perspective: Why the Tamper Phase Is Your Highest-Value Detection Window
The affiliate's mistake is your opportunity. The EDR-evasion phase has three properties that make it ideal for detection engineering:
- It happens before encryption — minutes to hours of runway to respond.
- It is loud by nature — stopping security services, loading unsigned/unusual kernel drivers, and editing Defender policy keys are behaviors with very low legitimate-activity baselines on end-user systems.
- Attackers must do it — there is no modern ransomware playbook that skips defense impairment.
If your SOC treats "EDR agent stopped reporting" or "security service deleted" as a page-worthy event, an Akira operator's anti-EDR step becomes a tripwire instead of a blind spot.
Detection & Response
The following detections target the specific behaviors documented in this incident class: security service termination, Defender tampering, vulnerable driver loads, and suspicious driver file drops. Every rule below is tuned against noise — deploy in monitor mode first if your environment has heavy administrative tooling overlap.
---
title: Security Product Service Termination via Command Line
description: Detects attempts to stop or delete security product services using sc.exe or net.exe, a hallmark of ransomware pre-encryption defense impairment as seen in Akira intrusions.
references:
- https://attack.mitre.org/techniques/T1562/001/
- https://www.infosecurity-magazine.com/news/akira-affiliate-crashes-ransomware/
author: Security Arsenal
date: 2026/02/10
status: experimental
logsource:
category: process_creation
product: windows
detection:
selection_binary:
Image|endswith:
- '\sc.exe'
- '\net.exe'
- '\net1.exe'
selection_action:
CommandLine|contains:
- 'stop'
- 'delete'
- 'disable'
selection_target:
CommandLine|contains:
- 'WinDefend'
- 'Sense'
- 'SentinelAgent'
- 'CSFalconService'
- 'HuntressAgent'
- 'Sophos'
- 'CarbonBlack'
- 'CbDefense'
- 'MsMpEng'
- 'ElasticAgent'
- 'cyserver'
condition: selection_binary and selection_action and selection_target
falsepositives:
- Legitimate EDR upgrades or scripted agent reinstalls by IT
- Managed service provider maintenance windows
level: high
---
title: Windows Defender Tampering via Registry or PowerShell
description: Detects registry-based Defender disabling and Set-MpPreference abuse consistent with ransomware operator defense evasion before payload detonation.
references:
- https://attack.mitre.org/techniques/T1562/001/
- https://www.infosecurity-magazine.com/news/akira-affiliate-crashes-ransomware/
author: Security Arsenal
date: 2026/02/10
status: experimental
logsource:
category: process_creation
product: windows
detection:
selection_reg:
Image|endswith: '\reg.exe'
CommandLine|contains:
- 'Windows Defender'
- 'DisableAntiSpyware'
- 'DisableRealtimeMonitoring'
- 'DisableBehaviorMonitoring'
- 'DisableOnAccessProtection'
selection_ps:
Image|endswith:
- '\powershell.exe'
- '\pwsh.exe'
CommandLine|contains:
- 'Set-MpPreference'
CommandLine|contains:
- '-DisableRealtimeMonitoring $true'
- '-DisableBehaviorMonitoring $true'
- '-DisableIOAVProtection $true'
- 'Add-MpPreference -ExclusionPath'
- '-ExclusionPath C:'
- '-ExclusionProcess'
condition: 1 of selection_*
falsepositives:
- Rare: documented IT exclusion changes — alert and verify against change tickets
level: high
---
title: Suspicious Kernel Driver Load — BYOVD EDR Killer Indicators
description: Detects loading of drivers from non-standard paths commonly abused in Bring Your Own Vulnerable Driver attacks used to terminate EDR from kernel mode, as attempted by the Akira affiliate.
references:
- https://attack.mitre.org/techniques/T1068/
- https://attack.mitre.org/techniques/T1562/001/
- https://www.infosecurity-magazine.com/news/akira-affiliate-crashes-ransomware/
author: Security Arsenal
date: 2026/02/10
status: experimental
logsource:
category: driver_load
product: windows
detection:
selection_path:
ImageLoaded|contains:
- '\Users\Public\'
- '\AppData\'
- '\Temp\'
- '\ProgramData\'
- '\Windows\Temp\'
- '\Perflogs\'
filter_legit:
Signed: 'true'
SignatureStatus: 'valid'
condition: selection_path and not filter_legit
falsepositives:
- Some legitimate OEM utilities load drivers from ProgramData — baseline per environment
level: critical
// Hunt: Akira-style pre-encryption defense impairment
// Looks for security service tampering, Defender manipulation, and suspicious driver drops
// across a 7-day window, correlated to a single host for triage efficiency.
let Lookback = 7d;
let SecurityTargets = dynamic(["WinDefend","Sense","SentinelAgent","CSFalconService","HuntressAgent","MsMpEng","CbDefense","Sophos","cyserver"]);
let ServiceTamper =
DeviceProcessEvents
| where Timestamp > ago(Lookback)
| where FileName in~ ("sc.exe","net.exe","net1.exe","taskkill.exe","powershell.exe","pwsh.exe","reg.exe")
| where ProcessCommandLine has_any (SecurityTargets)
or ProcessCommandLine has_any ("DisableAntiSpyware","DisableRealtimeMonitoring","Set-MpPreference","ExclusionPath")
| project ServiceTamperTime=Timestamp, DeviceName, FileName, ProcessCommandLine, AccountName, InitiatingProcessFileName;
let DriverDrop =
DeviceFileEvents
| where Timestamp > ago(Lookback)
| where FileName endswith ".sys"
| where FolderPath has_any ("\\Users\\Public\\","\\AppData\\","\\Temp\\","\\ProgramData\\","\\Perflogs\\")
| project DriverDropTime=Timestamp, DeviceName, FileName, FolderPath, SHA256, InitiatingProcessFileName;
ServiceTamper
| join kind=fullouter DriverDrop on DeviceName
| extend EarliestActivity = min_of(ServiceTamperTime, DriverDropTime)
| summarize Activities = make_set(strcat(FileName, " :: ", ProcessCommandLine)),
DroppedDrivers = make_set(FolderPath),
FirstSeen = min(EarliestActivity),
LastSeen = max(iff(isnull(DriverDropTime), ServiceTamperTime, DriverDropTime))
by DeviceName, AccountName
| sort by FirstSeen asc;
-- Hunt: EDR tampering artifacts and suspicious driver staging on Windows endpoints
-- Targets: driver files in user-writable paths, deleted/stopped security services,
-- and Defender tamper registry keys. Deploy as a fleet-wide Velociraptor hunt.
-- Artifact 1: Driver files staged outside System32\drivers
LET drivers = SELECT FullPath AS DriverPath,
Mtime AS Modified,
Size
FROM glob(globs=[
'C:/Users/Public/**/*.sys',
'C:/Windows/Temp/**/*.sys',
'C:/ProgramData/**/*.sys',
'C:/Users/*/AppData/**/*.sys'
])
WHERE Modified > now() - 604800 -- last 7 days
SELECT DriverPath, Modified, Size FROM drivers
-- Artifact 2: Defender tamper registry keys
SELECT FullPath AS RegKey,
Data.value AS RegValue,
Mtime AS LastWrite
FROM glob(globs='HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows Defender/*',
accessor='registry')
WHERE RegKey =~ 'DisableAntiSpyware|DisableRealtimeMonitoring'
OR RegValue = 0x1
-- Artifact 3: Processes holding handles to known EDR-killer service names
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(sc (stop|delete)|net stop|taskkill).*(WinDefend|Sense|SentinelAgent|CSFalcon|Huntress|MsMpEng)'
# Akira Defense-Impairment Hardening & Verification Script
# Run elevated on Windows endpoints/servers. Verifies the controls that stop
# EDR-killer tradecraft: Tamper Protection, vulnerable driver blocklist,
# and real-time monitoring state.
Write-Host "=== [1/5] Defender Tamper Protection Status ===" -ForegroundColor Cyan
$mp = Get-MpComputerStatus
$tp = Get-MpPreference | Select-Object -ExpandProperty DisableRealtimeMonitoring
Write-Host ("Real-Time Monitoring Disabled : {0}" -f $tp)
Write-Host ("Tamper Protection Enabled : {0}" -f $mp.IsTamperProtected)
if (-not $mp.IsTamperProtected) {
Write-Warning "Tamper Protection is OFF. Enable it in the Microsoft Defender portal (Intune/Manual) — this is the single highest-value control against ransomware EDR evasion."
}
Write-Host "`n=== [2/5] Microsoft Vulnerable Driver Blocklist ===" -ForegroundColor Cyan
$vdb = Get-CimInstance -Namespace "root\Microsoft\Windows\Defender" -ClassName MSFT_MpPreference -ErrorAction SilentlyContinue
$hvci = (Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard -ErrorAction SilentlyContinue).SecurityServicesRunning
Write-Host "HVCI / Memory Integrity state : $hvci"
Write-Host "Verify 'Microsoft Vulnerable Driver Blocklist' is enabled: Defender portal > ASR or Smart App Control settings. Blocklist requires HVCI or SACA on supported builds."
Write-Host "`n=== [3/5] Defender Exclusions Audit (ransomware operators abuse these) ===" -ForegroundColor Cyan
$pref = Get-MpPreference
if ($pref.ExclusionPath -or $pref.ExclusionProcess) {
Write-Warning "Exclusions present — validate every entry against approved change records:"
$pref.ExclusionPath | ForEach-Object { Write-Host " Path : $_" }
$pref.ExclusionProcess| ForEach-Object { Write-Host " Process: $_" }
} else {
Write-Host "No exclusions configured. Good."
}
Write-Host "`n=== [4/5] Security Service Integrity Check ===" -ForegroundColor Cyan
$services = @("WinDefend","Sense","WdNisSvc","HuntressAgent")
foreach ($svc in $services) {
$s = Get-Service -Name $svc -ErrorAction SilentlyContinue
if ($s) {
$color = if ($s.Status -eq 'Running' -and $s.StartType -ne 'Disabled') { 'Green' } else { 'Red' }
Write-Host (" {0,-15} Status: {1,-10} StartType: {2}" -f $svc, $s.Status, $s.StartType) -ForegroundColor $color
if ($s.StartType -eq 'Disabled') { Write-Warning "$svc is DISABLED — treat as a potential tampering indicator." }
}
}
Write-Host "`n=== [5/5] Suspicious .sys Files in User-Writable Paths (last 7 days) ===" -ForegroundColor Cyan
$paths = @("$env:PUBLIC","$env:TEMP","C:\ProgramData","C:\Windows\Temp")
foreach ($p in $paths) {
Get-ChildItem -Path $p -Recurse -Filter *.sys -ErrorAction SilentlyContinue |
Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) } |
ForEach-Object { Write-Warning ("Suspicious driver file: {0} (modified {1})" -f $_.FullName, $_.LastWriteTime) }
}
Write-Host "`nVerification complete. Escalate any RED/WARNING findings to IR." -ForegroundColor Cyan
Remediation and Hardening Recommendations
The Akira affiliate's failure was partly luck. Do not build your program on luck. These are the controls, in priority order, that convert "attacker self-sabotage" into "attacker stopped by design":
- Enable and enforce Tamper Protection on every endpoint. For Microsoft Defender for Endpoint, Tamper Protection must be managed from the Defender portal or Intune — local administrators cannot disable it when properly configured. Audit for endpoints where it is off; treat any endpoint reporting a tamper state change as a high-severity alert.
- Enable Microsoft's Vulnerable Driver Blocklist and HVCI (Memory Integrity). This directly counters the BYOVD EDR-killer pattern Akira affiliates favor. On Windows 11 22H2+ and current Server builds, verify via
msinfo32or Device Guard WMI that the blocklist is active. Where supported, deploy a WDAC policy restricting driver loads to your approved inventory. - Alert on EDR agent silence, not just EDR alerts. Build a heartbeat monitor: any managed endpoint that stops checking in with your EDR platform for more than a defined threshold (15–30 minutes for servers) generates a page-worthy incident. This catches both successful tampering and failed tampering that destabilizes the agent — exactly what happened in the Huntress case.
- Lock down Defender exclusions. Exclusions are the most abused legitimate mechanism in ransomware pre-encryption staging. Enforce exclusions centrally via Intune/GPO so local admins (and compromised admin accounts) cannot add them, and continuously audit the existing exclusion list.
- Harden the initial access vectors Akira actually uses. Enforce phishing-resistant MFA on all VPN/remote access gateways (Cisco ASA/FTD SSL VPN remains a top Akira entry point — audit for VPN concentrators still on password-only auth), disable or broker RDP, and rotate credentials for any service accounts touching backup infrastructure. Review the joint CISA/FBI Akira advisory (cisa.gov, AA-109A and subsequent updates) for current IOCs and TTP guidance.
- Protect backups as if they are already targeted. Akira affiliates delete shadow copies and hunt backup infrastructure before encryption. Use immutable/offline backup copies, separate backup credentials from domain admin, and alert on
vssadmin delete shadows,wbadmin delete, andbcdeditrecovery-disable commands. - Drill the "tamper alert" response path. Your runbook for a security-service-stopped alert should include immediate host isolation at the network layer (EDR may be untrustworthy), memory capture before reboot, and fleet-wide hunting for the same driver/service artifacts. Speed matters: the window between defense impairment and encryption is often under an hour.
The uncomfortable takeaway from the Huntress reporting: this victim survived because the attacker fumbled, not because a control fired in time. A different affiliate — one who tested their EDR killer before deployment — would have completed the encryption. Close the gap now, while the threat actors are still making your job easy.
Related Resources
Security Arsenal Managed SOC Services AlertMonitor Platform Book a SOC Assessment soc-mdr Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.