Windows Network Connections to azurewebsites.net from Non-Browser Processes

Alerts on outbound connections to azurewebsites.net started by non-browser processes on Windows.

FreeReviewedSigma · Medium · v2
Product
windows
Category
network_connection
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2024-06-24
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 identifies initiated outbound network connections from a Windows host to a destination hostname ending with "azurewebsites.net" where the initiating process is not one of the listed common browser or related application executables. Attackers may use cloud-hosted endpoints for command-and-control, payload hosting, or data exfiltration, making unexpected non-browser egress to this domain notable. It relies on network connection telemetry that includes whether the connection was initiated, the destination hostname, and the full process image path.

Related detections9 linkedT1102 — drag to rearrange
Windows Executable Connections to Dead Drop Resolver Domains Excluding Common Browsers
Possible Telegram API Command and Control DNS Query
Malicious Anubis Ransomware Cloudflare Tunnel via cloudflared (via process_creation)
Possible DNS Queries to Public Ethereum RPC Endpoints for EtherHiding Payload Retrieval (via dns_query)
Possible ITG05 Headlace Staging via Mocky and Mockbin Services (via proxy)
PowerShell Remote Download From Bunny CDN Host
Suspicious DNS Query for TryCloudflare Tunnel Abused for Malware Delivery (via dns_query)
Possible Access-Code Validation Beacon to Malware Delivery C2 (via proxy)
Suspicious Payload Retrieval from Cloudflare Tunnel via LOLBin (via process_creation)
Windows Network Connections to azurewebsites.net from Non-Browser Processes
Pivot detection · T1102 · 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.