huntrule

Windows Application: ScreenConnect RMM File Transfer Activity (Event 201)

Flags ScreenConnect RMM file transfer events on Windows based on provider name, Event ID 201, and transfer action text.

FreeReviewedSigma · Low · v2
Product
windows
Service
application
Author
Ali Alwashali (SigmaHQ), DRL 1.1
Published
2023-10-10
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Execution

  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. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies file transfer activity initiated or handled through ScreenConnect on Windows by matching an application event where the provider is ScreenConnect and the event indicates a file transfer action. Attackers can use ScreenConnect for stealthy remote administration, including moving files to support payload staging or data movement. Detection relies on Windows application telemetry containing the provider name and the specific event text indicating “Transferred files with action.”

Reporting behind it

Related detections9 linkedT1059.003 — drag to rearrange
Suspicious IP Release and Renew via Minimized cmd During Driver Install
Malicious IIS Worker Spawning nslookup via WS_FTP Deserialization
Malicious Metasploit Reverse Shell Injection in SQL Server (via process_creation)
Suspicious Fake Crypto Wallet Installer Batch Script Staging (via file_event)
Obfuscated Encoded PowerShell Payload Deployed via Process Execution (via process_creation)
Operator Bloopers Cobalt Strike Modules
Malicious KB Document Masqueraded Executable Spawned by Script Interpreter via RoKRAT Loader (via process_creation)
Malicious SCMBanker ClickFix Payload Fetch via Curl Piped to Cmd
Malicious Payload Assembly via MZ Header Prepend and copy Concatenation (via process_creation)
Windows Application: ScreenConnect RMM File Transfer Activity (Event 201)
Pivot detection · T1059.003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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