This hypothesis targets the presence of known Mozi botnet URLs, which are frequently used for command-and-control (C2) communications or initial payload delivery in IoT and server environments. Proactively hunting for these indicators in Azure Sentinel allows the SOC to identify compromised assets before the botnet can propagate laterally or execute malicious tasks, mitigating the risk of large-scale network disruption.
Threat: Mozi Total URLs: 26 Active URLs: 21
| URL | Status | Threat | Date Added |
|---|---|---|---|
hxxp://222.141.75.218:42500/i | online | malware_download | 2026-09-21 |
hxxp://123.8.63.177:44082/bin.sh | online | malware_download | 2026-09-21 |
hxxp://115.63.149.175:48396/i | online | malware_download | 2026-09-21 |
hxxp://115.51.121.117:33014/i | offline | malware_download | 2026-09-21 |
hxxp://123.12.86.205:38218/i | online | malware_download | 2026-09-21 |
hxxp://59.180.150.177:38357/bin.sh | online | malware_download | 2026-09-21 |
hxxp://59.180.141.192:49773/i | online | malware_download | 2026-09-21 |
hxxp://119.178.251.26:60563/i | online | malware_download | 2026-09-21 |
hxxp://123.12.160.14:42722/i | online | malware_download | 2026-09-21 |
hxxp://115.61.113.254:45518/i | online | malware_download | 2026-09-21 |
hxxp://123.12.86.205:38218/bin.sh | online | malware_download | 2026-09-21 |
hxxp://115.56.96.49:56798/i | online | malware_download | 2026-09-21 |
hxxp://125.41.8.190:45393/i | online | malware_download | 2026-09-21 |
hxxp://125.42.8.66:45720/i | online | malware_download | 2026-09-21 |
hxxp://125.41.8.190:45393/bin.sh | online | malware_download | 2026-09-21 |
hxxp://182.126.249.231:50800/bin.sh | online | malware_download | 2026-09-21 |
hxxp://61.52.42.131:50755/i | online | malware_download | 2026-09-21 |
hxxp://61.52.42.131:50755/bin.sh | online | malware_download | 2026-09-21 |
hxxp://59.96.140.242:56865/bin.sh | online | malware_download | 2026-09-21 |
hxxp://59.96.140.242:56865/i | offline | malware_download | 2026-09-21 |
hxxp://182.126.126.236:40817/i | online | malware_download | 2026-09-21 |
hxxp://115.55.225.187:35091/i | offline | malware_download | 2026-09-21 |
hxxp://219.156.114.110:51923/i | offline | malware_download | 2026-09-21 |
hxxp://182.126.126.236:40817/bin.sh | offline | malware_download | 2026-09-21 |
hxxp://219.155.209.247:42165/i | online | malware_download | 2026-09-21 |
// Hunt for DNS resolution of URLhaus malicious domains
// Threat: Mozi
let malicious_domains = dynamic(["61.52.42.131", "123.8.63.177", "115.56.96.49", "182.126.126.236", "115.55.249.142", "115.63.149.175", "123.12.86.205", "119.178.251.26", "125.41.8.190", "115.61.113.254", "125.42.8.66", "182.126.249.231", "123.12.160.14", "222.141.75.218", "59.180.141.192", "59.96.140.242", "59.180.150.177", "219.155.209.247"]);
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(["61.52.42.131", "123.8.63.177", "115.56.96.49", "182.126.126.236", "115.55.249.142", "115.63.149.175", "123.12.86.205", "119.178.251.26", "125.41.8.190", "115.61.113.254", "125.42.8.66", "182.126.249.231", "123.12.160.14", "222.141.75.218", "59.180.141.192", "59.96.140.242", "59.180.150.177", "219.155.209.247"]);
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 |
Scenario: A network operations center (NOC) engineer is performing a manual health check on a legacy IoT device or industrial control system (ICS) node that has been isolated but not yet decommissioned. The engineer uses a browser or curl to ping the device’s default HTTP endpoint (e.g., http://192.168.10.5:8080/status) to verify connectivity before a firmware update. If this specific IP/port combination matches one of the 26 Mozi URLs in the hunt package (often associated with default ports like 80, 8080, or 443 on compromised hosts), the rule will trigger.
NOC_Engineers or Field_Tech security group AND the destination port is in the standard HTTP/HTTPS range (80, 443, 8080, 8443). Alternatively, exclude if the destination host is tagged with the asset label Legacy_IoT or ICS_Isolated.Scenario: A DevOps engineer is running a scheduled cron job or Systemd timer on a CI/CD build agent to fetch configuration files or health metrics from a staging environment service. The job uses wget or curl to download a JSON status file from a known internal URL (e.g., http://staging-config.internal:8080/health) that happens to share the same host/port pattern as a Mozi URL in the dataset. Since Mozi often exploits default web server ports, this legitimate automated task can mimic the malicious beaconing behavior.
cron, systemd, ansible, or jenkins-agent AND the destination host