Azure Identity Risk: Sign-ins from Malware-Infected IP Addresses

Flags Azure sign-in risk events originating from malware-infected IP addresses linked to bot-server communication.

FreeReviewedSigma · High · v5
Product
azure
Service
riskdetection
Author
Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo' (SigmaHQ), DRL 1.1
Published
2023-09-03
Updated
2026-07-31

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 sign-in risk events where the source IP is identified as a malware-infected IP address. Attackers can use compromised infrastructure to blend in with legitimate authentication flows and establish command-and-control communications. The detection relies on Azure risk telemetry identifying riskEventType as malwareInfectedIPAddress.

Related detections9 linkedT1090 — drag to rearrange
Malicious Java Backdoor Execution from Public Documents via javaw (via process_creation)
Suspicious Proxyware Installation via accept-tos Flag on Linux
Suspicious DNS Query to Dynamic DNS and Tunneling Providers Abused by RATs
Malicious GenAI Browser Extension C2 and PAC Redirection (via proxy)
Malicious FRP Reverse Proxy Tunnel Identified by Hardcoded Token (via process_creation)
Suspicious SSH Reverse Tunnel Over DNS Port
Suspicious Chisel SOCKS Tunnel Command Line
Suspicious Cloudflare Quick Tunnel Used for Covert Access (via dns_query)
Suspicious SOCKS Proxy Autorun Registry Persistence via Registry Set
Azure Identity Risk: Sign-ins from Malware-Infected IP Addresses
Pivot detection · T1090 · 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.