This hypothesis posits that adversaries are leveraging a set of thirty-two specific 32-bit malicious URLs identified by URLhaus to deliver payloads or facilitate command and control communications within the network. A proactive hunt in Azure Sentinel is critical because early detection of these known malicious endpoints can prevent initial compromise vectors, allowing the SOC team to isolate affected assets before lateral movement occurs.
Threat: 32-bit Total URLs: 20 Active URLs: 16
| URL | Status | Threat | Date Added |
|---|---|---|---|
hxxp://222.127.77.227:51520/i | online | malware_download | 2026-07-27 |
hxxp://27.215.45.91:55255/i | online | malware_download | 2026-07-27 |
hxxp://77.247.88.81:49544/i | online | malware_download | 2026-07-27 |
hxxp://27.215.45.91:55255/bin.sh | online | malware_download | 2026-07-27 |
hxxp://103.44.136.115:40363/i | online | malware_download | 2026-07-27 |
hxxp://103.44.136.115:40363/bin.sh | online | malware_download | 2026-07-27 |
hxxp://119.116.38.141:51501/bin.sh | offline | malware_download | 2026-07-27 |
hxxp://222.138.149.25:37984/i | online | malware_download | 2026-07-27 |
hxxp://125.44.34.100:54105/i | online | malware_download | 2026-07-27 |
hxxp://2.183.135.123:46360/i | online | malware_download | 2026-07-27 |
hxxp://175.149.73.167:52513/i | online | malware_download | 2026-07-27 |
hxxp://182.112.176.29:36020/i | online | malware_download | 2026-07-27 |
hxxp://27.215.108.28:50461/i | online | malware_download | 2026-07-27 |
hxxp://175.149.73.167:52513/bin.sh | offline | malware_download | 2026-07-27 |
hxxp://182.112.176.29:36020/bin.sh | online | malware_download | 2026-07-27 |
hxxp://27.215.108.28:50461/bin.sh | online | malware_download | 2026-07-27 |
hxxp://110.178.50.118:55930/i | online | malware_download | 2026-07-27 |
hxxp://110.178.50.118:55930/bin.sh | offline | malware_download | 2026-07-27 |
hxxp://115.63.132.215:49858/bin.sh | offline | malware_download | 2026-07-27 |
hxxp://175.150.26.8:44311/i | online | malware_download | 2026-07-27 |
// Hunt for DNS resolution of URLhaus malicious domains
// Threat: 32-bit
let malicious_domains = dynamic(["2.183.135.123", "103.44.136.115", "175.150.26.8", "27.215.108.28", "27.215.45.91", "77.247.88.81", "175.149.73.167", "125.44.34.100", "222.138.149.25", "222.127.77.227", "110.178.50.118", "182.112.176.29"]);
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(["2.183.135.123", "103.44.136.115", "175.150.26.8", "27.215.108.28", "27.215.45.91", "77.247.88.81", "175.149.73.167", "125.44.34.100", "222.138.149.25", "222.127.77.227", "110.178.50.118", "182.112.176.29"]);
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 |
Here are 4 specific false positive scenarios for the URLhaus: 32-bit Malicious URLs detection rule, along with recommended filters and exclusions:
Scenario: Legacy Administrative Tool Connectivity
User-Agent string containing SCCM or SolarWinds, combined with a whitelist of known vendor domains (e.g., *.microsoft.com, *.solarwinds.com). Alternatively, exclude traffic originating from specific Service Accounts used by these tools.Scenario: Scheduled 32-bit Backup and Reporting Jobs
02:00–04:00 daily) or exclude specific process paths (e.g., C:\Program Files (x86)\Veeam\Backup\...) that initiate the request.Scenario: Third-Party Integration Webhooks