Windows: TacticalRMM Agent Installed with API/Auth Flags Pointing to Remote RMM Server

Alerts when TacticalRMM agent starts with --api/--auth and identity flags consistent with connecting to a configured remote RMM server.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Ahmed Nosir (@egycondor) (SigmaHQ), DRL 1.1
Published
2025-05-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 process creations where the TacticalRMM agent executable is launched with command-line parameters that include --api, --auth, and related identity flags such as --client-id and --site-id. Those flags indicate the agent is being configured to authenticate and connect to a specified remote RMM server. This matters because configuring an agent for silent remote management can be abused to establish command-and-control through attacker-controlled infrastructure. The detection relies on Windows process creation telemetry containing the executable path and full command line arguments.

Related detections9 linkedT1105 — drag to rearrange
Suspicious Velociraptor Agent Deployment via msiexec From Cloud Storage
Suspicious node.exe or code.exe Execution from Public Music Directory
Suspicious File Creation by OpenEDR ITSMService on Windows
Suspicious Remote Script Transfer via Bitsadmin (via process_creation)
Suspicious PowerShell Download Cradle via ClickFix Fake CAPTCHA (via process_creation)
Malicious Curl MSI Download to ProgramData via Process Creation
Suspicious CloudZ RAT Payload Download via curl to ProgramData
Suspicious n8n Campaign RMM Installer Masquerading as OneDrive Document
Suspicious PowerShell Download of lib.zip Archive
Windows: TacticalRMM Agent Installed with API/Auth Flags Pointing to Remote RMM Server
Pivot detection · T1105 · 9 related

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