huntrule

Windows DNS Client: DNS queries containing "ufile.io"

Alerts on Windows DNS Client queries where the queried name includes "ufile.io".

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

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

  14. Impact

What it detects

Identifies DNS Client operational events where the query name contains "ufile.io". Attackers may use this domain as part of data exfiltration infrastructure, so repeated or unexpected lookups warrant investigation. The rule relies on Windows Microsoft-Windows-DNS-Client/Operational telemetry, specifically EventID 3008 and the DNS query name field.

Reporting behind it

Related detections9 linkedT1567.002 — drag to rearrange
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)
Suspicious Data Exfiltration to Dropbox via curl (via process_creation)
Suspicious Lambda Function Creation Across Regions in AWS Extortion Operation
Malicious Data Exfiltration via Renamed Rclone Using Masqueraded Configuration
Windows DNS Client: DNS queries containing "ufile.io"
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.