This detection rule identifies adversary activity linked to the Mozi threat actor by monitoring specific Indicators of Compromise (IOCs) known to facilitate their initial access and lateral movement. SOC teams should proactively hunt for these signals in Azure Sentinel to rapidly identify early-stage intrusions, as Mozi’s sophisticated operations often target critical infrastructure where timely containment is essential to prevent data exfiltration or service disruption.
Malware Family: Mozi Total IOCs: 2 IOC Types: url
| Type | Value | Threat Type | First Seen | Confidence |
|---|---|---|---|---|
| url | hxxp://103[.]244[.]172[.]87:45274/Mozi.a | payload_delivery | 2026-07-26 | 75% |
| url | hxxp://130[.]12[.]209[.]147:55604/Mozi.m | payload_delivery | 2026-07-26 | 75% |
// Hunt for access to known malicious URLs
// Source: ThreatFox - Mozi
let malicious_urls = dynamic(["http://103.244.172.87:45274/Mozi.a", "http://130.12.209.147:55604/Mozi.m"]);
UrlClickEvents
| where Url has_any (malicious_urls)
| project Timestamp, AccountUpn, Url, ActionType, IsClickedThrough
| order by Timestamp desc
| Sentinel Table | Notes |
|---|---|
UrlClickEvents | Ensure this data connector is enabled |
Scenario: Scheduled Antivirus Definition Updates
ProcessName matches MsMpEng.exe (Defender) or RtkExe64.exe (Symantec) and the event timestamp falls within the configured maintenance window (e.g., 02:00–04:00 local time).Scenario: Automated Patch Deployment via Configuration Management
CommandLine containing keywords like “SCCM”, “Ansible”, or specific patch IDs (e.g., KB503...), and filter out events originating from the dedicated management server IP range (e.g., 192.168.10.5).Scenario: Third-Party Backup Agent Operations