Azure risk detection: Malicious IP sign-in risk event based on sign-in failure rate

Flags Azure risk events for sign-ins associated with malicious IPs using maliciousIPAddress failure-rate indications.

FreeReviewedSigma · High · v5
Product
azure
Service
riskdetection
Author
Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo' (SigmaHQ), DRL 1.1
Published
2023-09-07
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 Azure risk events where the risk event type is set to maliciousIPAddress. It indicates sign-in activity originating from an IP address classified as malicious, which attackers may use to probe accounts or attempt credential access. The detection relies on Azure risk detection telemetry that records the riskEventType value for these events.

Related detections9 linkedT1090 — drag to rearrange
Suspicious Flax Typhoon System Utility Masquerade Outside System32 via Renamed VPN Client (via process_creation)
Possible Credential Stuffing Blocked by Conditional Access in Microsoft 365
Possible ReverseSocks5 Tunneling Tool Execution on Linux (via process_creation)
Malicious GhostSocks Loader Execution with johnpidar Argument via process_creation
Malicious Chisel Reverse SOCKS Proxy Execution (via process_creation)
Malicious QEMU Covert Network Tunnel via User-Mode netdev Socket (via process_creation)
Malicious Tunneling Tool Execution on Linux Host (via process_creation)
Suspicious Chisel Reverse Tunnel Execution by UAT-9686
Suspicious macOS Trojan-Proxy LaunchAgent GoogleHelperUpdater Persistence (via file_event)
Azure risk detection: Malicious IP sign-in risk event based on sign-in failure rate
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.