T1583.006 Google Chronicle · YARA-L

Detect Web Services in Google Chronicle

Adversaries may register for web services that can be used during targeting. A variety of popular websites exist for adversaries to register for a web-based service that can be abused during later stages of the adversary lifecycle, such as during Command and Control (Web Service), Exfiltration Over Web Service, or Phishing. Using common services such as those offered by Google, GitHub, Discord, Telegram, or Dropbox makes it easier for adversaries to hide in expected noise. Real-world threat actors including APT29, Turla, Earth Lusca, Mustang Panda, Lazarus Group, HAFNIUM, MuddyWater, and Contagious Interview have all leveraged legitimate web platforms to host malware, stage C2 infrastructure, or receive exfiltrated data. Because the adversary's actual registration of these accounts occurs entirely outside the victim environment, detection pivots to identifying the operational use of these platforms by suspicious processes within monitored endpoints.

MITRE ATT&CK

Tactic
Resource Development
Technique
T1583 Acquire Infrastructure
Sub-technique
T1583.006 Web Services
Canonical reference
https://attack.mitre.org/techniques/T1583/006/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule t1583_006_web_services_suspicious_process_network {
  meta:
    author = "Argus Detection Engineering"
    description = "Detects LOLBin or scripting interpreter processes making outbound network connections to web service platforms commonly abused for C2, payload staging, or data exfiltration (T1583.006). Covers threat actors including APT29, Lazarus Group, MuddyWater, HAFNIUM, Turla, and Contagious Interview."
    mitre_attack_tactic = "Resource Development"
    mitre_attack_technique = "T1583.006"
    mitre_attack_technique_name = "Acquire Infrastructure: Web Services"
    severity = "HIGH"
    confidence = "MEDIUM"
    platform = "Windows"
    reference = "https://attack.mitre.org/techniques/T1583/006/"
    version = "1.0"

  events:
    $net.metadata.event_type = "NETWORK_CONNECTION"
    $net.principal.process.file.full_path != ""
    re.regex($net.principal.process.file.full_path,
      `(?i)(\\|/)+(powershell|pwsh|cmd|mshta|wscript|cscript|rundll32|regsvr32|certutil|bitsadmin|curl|python[w3]?|javaw?|msbuild|installutil|csc)\.exe$`)
    re.regex($net.target.hostname,
      `(?i)^(api\.github\.com|raw\.githubusercontent\.com|gist\.githubusercontent\.com|gist\.github\.com|api\.dropboxapi\.com|content\.dropboxapi\.com|www\.dropbox\.com|www\.googleapis\.com|drive\.google\.com|storage\.googleapis\.com|firebaseio\.com|firebase\.google\.com|api\.telegram\.org|discord\.com|discordapp\.com|cdn\.discordapp\.com|hooks\.discord\.com|pastebin\.com|rentry\.co|paste\.ee|hastebin\.com|trycloudflare\.com|workers\.dev|notion\.so|api\.notion\.com|graph\.microsoft\.com|onedrive\.live\.com|terabox\.com|sync\.com|onehub\.com|filemail\.com|file\.io)$`)

  condition:
    $net
}
high severity medium confidence

Google Chronicle YARA-L 2.0 rule matching NETWORK_CONNECTION UDM events where the principal process path resolves to a known LOLBin or scripting interpreter and the target hostname is an anchored match against the canonical list of web service platforms abused for C2, payload hosting, or exfiltration. The anchored regex prevents partial subdomain bypass (e.g., evil-api.github.com.attacker.tld) while retaining coverage of the exact domains observed in real-world campaigns.

Data Sources

Google Chronicle SIEMChronicle Unified Data Model (UDM)Google Cloud Security Command Center (SCC)Endpoint Detection and Response (EDR) telemetry forwarded to Chronicle

Required Tables

UDM NETWORK_CONNECTION events

False Positives & Tuning

  • Automated software packaging pipelines where MSBuild or Python interpreters resolve GitHub API or Google Cloud Storage hostnames to retrieve build dependencies, signing certificates, or release artifacts
  • DevOps engineers running PowerShell or cmd.exe scripts to interact with the Microsoft Graph API or OneDrive as part of approved SharePoint/M365 automation workflows
  • Security operations tooling that uses Java or Python to contact Firebase or Cloudflare Workers endpoints managed by the organisation's own threat intelligence or SOAR platform infrastructure
Download portable Sigma rule (.yml)

Other platforms for T1583.006


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1PowerShell Payload Retrieval from GitHub Raw Content

    Expected signal: Sysmon Event ID 1: Process Create with Image=powershell.exe, CommandLine containing 'Net.WebClient' and 'raw.githubusercontent.com'. Sysmon Event ID 3: Network Connection to raw.githubusercontent.com:443. Sysmon Event ID 22: DNS Query for raw.githubusercontent.com from powershell.exe. PowerShell ScriptBlock Log Event ID 4104 with the full script. DeviceNetworkEvents in MDE will show RemoteUrl matching raw.githubusercontent.com.

  2. Test 2Data Exfiltration Simulation to Dropbox API via curl

    Expected signal: Sysmon Event ID 3: Network Connection from curl.exe to content.dropboxapi.com:443. Sysmon Event ID 22: DNS Query for content.dropboxapi.com from curl.exe. Sysmon Event ID 11: File Create for the temp file. DeviceNetworkEvents in MDE will show InitiatingProcessFileName=curl.exe, RemoteUrl matching content.dropboxapi.com. The HTTP response will be 401, but the connection event is logged regardless.

  3. Test 3Telegram Bot API C2 Polling Simulation

    Expected signal: Sysmon Event ID 1: Process Create with Image=powershell.exe, CommandLine containing 'api.telegram.org' and 'getUpdates'. Sysmon Event ID 3: Network Connection from powershell.exe to api.telegram.org:443. Sysmon Event ID 22: DNS Query for api.telegram.org from powershell.exe. PowerShell ScriptBlock Log Event ID 4104 capturing the Invoke-RestMethod call. DeviceNetworkEvents in MDE shows RemoteUrl matching api.telegram.org.

  4. Test 4Multi-Stage Web Service Abuse — Payload Retrieval Then C2 Check-In

    Expected signal: Sysmon Event ID 1: Single powershell.exe process with long command line containing both pastebin.com and discord.com references. Sysmon Event ID 3: Two network connection events — one to pastebin.com:443, one to discord.com:443. Sysmon Event ID 22: Two DNS queries — pastebin.com and discord.com — both initiated by powershell.exe. PowerShell ScriptBlock Log Event ID 4104 with the full script. DeviceNetworkEvents in MDE shows two entries with RemoteUrl matching pastebin.com and discord.com respectively.

Unlock Pro Content

Get the full detection package for T1583.006 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections