Weird DNS queries from svchost.exe (google.com.onion, wildcard + malformed domains) · anyone seen this on Windows?
Source Reddit BlueTeam
Discussion
A Windows 11 host running svchost.exe generated unusual DNS queries including google.com.onion, wildcard, and malformed domains within a very short time frame. These queries returned NXDOMAIN responses and did not lead to any follow-up connections or IP resolutions. The behavior resembles synthetic or malformed DNS queries rather than user-initiated activity and is similar to DNS probing or spoof detection patterns observed on other devices. The source of these queries under svchost.exe is unclear, and it is uncertain whether this is normal Windows DNS client behavior, network validation, or triggered by security tools. No confirmed malicious activity or exploit is reported.
r/blueteamsec (opens in a new tab)u/Street-Rabbit-49660 points0 comments
I’m investigating a DNS-related alert and wanted to check if anyone has seen similar behavior in a Windows environment.
We observed the following DNS queries from a Windows 11 host:
google.com.onion*google.comwww.goooooooooooooooooooooooooooooooooooooooooooooooooooooooooogle.comgoogle.com
All of these were generated within the same second by:
svchost.exe- Running as
NT AUTHORITY\SYSTEM - Sysmon Event ID 22 (DNS query)
Some key observations:
- The
.onionquery returned NXDOMAIN (DNS_ERROR_RCODE_NAME_ERROR) - No follow-up connections or IP resolution were observed
- The behavior looks like a burst of synthetic / malformed queries rather than user activity
This pattern looks very similar to what people have reported on Samsung devices (MobileWIPS DNS probing / spoof detection), but this is a Windows endpoint.
Question:
- Has anyone seen similar DNS query patterns from
svchost.exeon Windows endpoints? - Could this be:
- DNS Client (Dnscache) behavior?
- Some Windows network validation / spoof detection logic?
- Or triggered indirectly by EDR/XDR tools interacting with DNS?
- Any reliable way to map this definitively to a specific service under
svchostusing logs alone?
At the moment, it looks benign (NXDOMAIN + no connections), but the .onion query is triggering alerts, so trying to confirm before suppressing.
Appreciate any insights.