Suspicious Azure WireServer Access via curl from Container

PremiumReviewedSigma · Medium · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-10-20
Updated
2026-10-20

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects command-line HTTP requests to the Azure host WireServer at 168.63.129.16 from a container or node. This behavior matches Dirty DAG where an attacker queried the Azure fabric and instance metadata to steal managed identity tokens. Direct curl or wget access to the WireServer address from workloads is anomalous and indicates cloud credential harvesting.

Related detections9 linkedT1552.005 — drag to rearrange
Possible Kubernetes Service Account Token Theft from Pod Secrets Path
Malicious Cloud Instance Metadata Token Theft via IMDS Identity Endpoint (via process_creation)
Suspicious GCP Metadata Service Token Access via Command Line (via process_creation)
Suspicious Bulk Kubernetes Secret Dump via Kubectl
Suspicious Cloud Instance Metadata Access via Command Line Tool
Suspicious Cloud Instance Metadata Credential Access via curl to IMDS (via process_creation)
Possible Jamf Pro SSRF Exploitation via eduFeatureSettingsTest imageUrl (via webserver)
Possible WebSphere Portal SSRF via Proxy Servlet targeting Cloud Metadata (CVE-2021-27748) (via webserver)
Possible SSRF to AWS Metadata via Workspace One UEM BlobHandler CVE-2021-22054
Suspicious Azure WireServer Access via curl from Container
Pivot detection · T1552.005 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.