Antivirus signature match for exploitation framework indicators

Alerts when AV signature names contain indicators tied to exploitation frameworks and related backdoors.

FreeReviewedSigma · Critical · v5
Category
antivirus
Author
Florian Roth (Nextron Systems), Arnim Rupp (SigmaHQ), DRL 1.1
Published
2018-09-09
Updated
2026-07-31

ATT&CK techniques

Execution → C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. Exfiltration

  12. Impact

What it detects

This rule flags Antivirus alerts whose signature text contains known exploitation framework and related payload/tool indicators (e.g., ATK/Cobalt, Metasploit, Meterpreter, PowerSploit). Such matches matter because attackers commonly deploy these tooling components to establish access, execute commands, or maintain command-and-control. The detection relies on Antivirus telemetry that records the signature name or alert text including the specified strings.

Related detections9 linkedT1219 — drag to rearrange
Antivirus signatures matching APT malware naming patterns
Antivirus Remote Access Tool Signature Matches Known RAT Names
Suspicious NetSupport client32 Execution from AppData
Suspicious n8n Campaign RMM Installer Masquerading as OneDrive Document
Suspicious Velociraptor Agent Deployment via msiexec From Cloud Storage
Malicious Scheduled Task Masquerading as GoogleUpdate Launching SSH Reverse Shell
Malicious NetSupport RAT Client32 Execution
Possible AnyDesk RMM Silent MSI Installation via Windows Installer (via process_creation)
Suspicious Outbound Connection To MoonPeak C2 High Ports
Antivirus signature match for exploitation framework indicators
Pivot detection · T1219 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.