Windows Suspicious Non-Browser Network Connections to Google API Endpoints

Alerts on suspicious Windows processes connecting to Google API hostnames, excluding common browsers and known benign apps.

FreeReviewedSigma · Medium · v2
Product
windows
Category
network_connection
Author
Gavin Knapp (SigmaHQ), DRL 1.1
Published
2023-05-01
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 network connections from non-browser Windows processes to common Google API domains such as drive.googleapis.com, oauth2.googleapis.com, sheets.googleapis.com, and www.googleapis.com. Such traffic from unexpected binaries may indicate covert command-and-control or automation using Google-hosted services. It relies on Windows network connection telemetry that includes destination hostname and the connecting process image path, using allowlisting for common browsers and related executables to reduce false positives.

Related detections9 linkedT1102 — drag to rearrange
Possible Telegram API Command and Control DNS Query
Malicious Anubis Ransomware Cloudflare Tunnel via cloudflared (via process_creation)
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)
Suspicious Malware Delivery via Discord CDN Attachment
Suspicious PowerShell Communication with Dropbox API (via ps_script)
Windows Suspicious Non-Browser Network Connections to Google API Endpoints
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.