Windows DNS Client: DNS query for anonfiles.com domain

Alerts when Windows DNS client logs show a DNS query containing .anonfiles.com.

FreeReviewedSigma · High · v2
Product
windows
Service
dns-client
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-01-16
Updated
2026-07-31

ATT&CK techniques

Exfiltration
  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. C2

  13. Impact

What it detects

This rule identifies DNS client activity where the DNS query name contains the .anonfiles.com domain. Attackers may use file-hosting services to move or stage data, and matching DNS queries helps surface potential infrastructure and exfiltration-related communication. It relies on Microsoft-Windows-DNS Client operational event telemetry, specifically events with EventID 3008 and a matching query name substring.

Related detections9 linkedT1567.002 — drag to rearrange
Malicious Cloud Credential Enumeration Piped to Network Exfiltration (via process_creation)
Possible Dropbox API C2 Channel via Non-Browser DNS Query
Suspicious Data Exfiltration to Wasabi Cloud via rclone (via process_creation)
Suspicious Data Exfiltration via rclone Cloud Transfer (via process_creation)
Malicious Data Exfiltration to MEGA and FTP via rclone Multi-Threaded Copy (via process_creation)
Malicious Data Exfiltration to MEGA via Rclone
Malicious Silver Fox Stealer Exfiltration Using WhatsAppBackup User Agent
Suspicious Data Exfiltration to Azure Blob Storage via AzCopy (via process_creation)
Suspicious Data Exfiltration via Rclone Cloud Transfer (via process_creation)
Windows DNS Client: DNS query for anonfiles.com domain
Pivot detection · T1567.002 · 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.