Windows AnyDesk Executed from Suspicious Directory

Alerts on AnyDesk execution from non-standard folders on Windows, indicating potential remote access abuse.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-05-20
Updated
2026-07-30

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule flags process creation events where AnyDesk-related executables (AnyDesk.exe or AnyDeskMSI.exe) are started with metadata indicating AnyDesk, but the process path is not located in common AnyDesk installation locations. Attackers may abuse legitimate remote access software to establish interactive command-and-control capabilities, making unexpected execution paths a useful indicator of compromise. It relies on Windows process creation telemetry, including executable image paths and product/company/description fields.

Related detections9 linkedT1219 — drag to rearrange
Possible AnyDesk RMM Silent MSI Installation via Windows Installer (via process_creation)
macOS Process Creation: MeshAgent Remote Access via --meshServiceName
Windows MeshAgent Remote Access Tool Command Line Execution Indicators
Windows Process Creation: Microsoft QuickAssist.exe Execution
Windows MeshAgent remote command execution via cmd.exe or PowerShell child processes
Windows Incoming AnyDesk Connection via AnyDesk.exe or AnyDeskMSI.exe
Windows File Drop Indicators for RemoteKrbRelay SMB Relay Secret Dump Module
Windows DNS Queries to azurewebsites.net From Non-Browser Processes
Windows CSharp Streamer RAT Potentially Loaded .NET Executable from Temp dat####.tmp
Windows AnyDesk Executed from Suspicious Directory
Pivot detection · T1219 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.