Windows: Suspicious Velociraptor Child Process Execution Indicators

Alerts when Velociraptor.exe spawns specific child processes tied to tunneling, msiexec web installs, or PowerShell download commands.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-08-29
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 Windows process creation where Velociraptor.exe spawns child processes with command lines indicative of tool execution, remote access tunneling, or staged payload retrieval. Such activity matters because attackers can abuse DFIR tooling to blend in while launching additional components using web downloads and scripting. It relies on process creation telemetry, specifically the parent executable path and the child process command line or image name patterns.

Related detections9 linkedT1219 — drag to rearrange
Suspicious AnyDesk Unattended Access Configuration via Command Line (via process_creation)
Suspicious NetSupport client32 Persistence via Run Key from ProgramData
Suspicious Atera Agent Silent Onboarding via Process Creation
Suspicious Remote Access Tool User Agent in Outbound Traffic via Proxy
Suspicious ScreenConnect Remote Access Binary Running Under a Renamed Executable
Malicious Silent AteraAgent RMM Installation via IntegratorLogin
Possible Remote Monitoring and Management Tool Abuse for Remote Access
Suspicious NetSupport Manager Client Executing From ProgramData via Process Creation (via process_creation)
Malicious PowerShell Download Cradle Spawned by Quick Assist
Windows: Suspicious Velociraptor Child Process Execution Indicators
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.