This hunt targets the execution of known CoinMiner payloads delivered via malicious URLs, indicating an adversary is actively attempting to leverage organizational compute resources for cryptocurrency mining. Proactively hunting for these specific indicators in Azure Sentinel allows the SOC to identify compromised endpoints before resource-intensive mining operations degrade performance or establish persistence through additional malicious downloads.
Threat: CoinMiner Total URLs: 2 Active URLs: 2
| URL | Status | Threat | Date Added |
|---|---|---|---|
hxxp://192.162.199.246/m3/controller.exe | online | malware_download | 2026-09-14 |
hxxp://192.162.199.246/m2/mKM65Cf6QNqeOVw9.exe | online | malware_download | 2026-09-14 |
// Hunt for DNS resolution of URLhaus malicious domains
// Threat: CoinMiner
let malicious_domains = dynamic(["192.162.199.246"]);
DnsEvents
| where Name has_any (malicious_domains)
| project TimeGenerated, Computer, Name, IPAddresses
| order by TimeGenerated desc
// Hunt for web traffic to URLhaus malicious domains
let malicious_domains = dynamic(["192.162.199.246"]);
CommonSecurityLog
| where RequestURL has_any (malicious_domains) or DestinationHostName has_any (malicious_domains)
| project TimeGenerated, SourceIP, RequestURL, DestinationHostName, DeviceAction
| order by TimeGenerated desc
| Sentinel Table | Notes |
|---|---|
CommonSecurityLog | Ensure this data connector is enabled |
DnsEvents | Ensure this data connector is enabled |
10.20.5.0/24) when the User-Agent string contains “HealthCheck” or “CanaryProbe”, or exclude the specific process name (e.g., java.exe or tomcat.exe) if the destination port is 80/443 and the request method is GET.curl or wget to fetch metadata from a public registry or CDN that has been temporarily compromised or misconfigured to serve CoinMiner payloads, or the pipeline explicitly tests outbound connectivity to a list of “known good” URLs that includes one of the CoinMiner domains for latency benchmarking.
curl.exe, wget.exe, or python.exe (running a script) and the source host is tagged with the environment label ci-cd or build-server, provided the destination URL is in the allowlist of benchmarking endpoints.chrome.exe, firefox.exe,