This detection identifies adversary activity involving known malicious URLs from the IP range 45.88.186.163, which are frequently associated with phishing campaigns and malware distribution. Proactively hunting for these specific indicators in Azure Sentinel allows the SOC team to rapidly isolate compromised endpoints and prevent lateral movement before broader network impact occurs.
Threat: 45-88-186-163 Total URLs: 2 Active URLs: 0
| URL | Status | Threat | Date Added |
|---|---|---|---|
hxxps://45.88.186.163/Bin/ScreenConnect.ClientSetup.exe | offline | malware_download | 2026-08-01 |
hxxps://45.88.186.163/bin/support.client.exe | offline | malware_download | 2026-08-01 |
// Hunt for DNS resolution of URLhaus malicious domains
// Threat: 45-88-186-163
let malicious_domains = dynamic(["45.88.186.163"]);
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(["45.88.186.163"]);
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: 45-88-186-163 Malicious URLs detection rule, including suggested filters and exclusions tailored for a legitimate enterprise environment:
Scenario: Automated Security Scanner Traffic
45-88-186-163 is part of a trusted cloud infrastructure or CDN node used by the scanner.Tenable.Nessus, QualysGuard, or Rapid7, suppress the alert.Scenario: Scheduled Cloud Backup & Sync Jobs
45-88-186-163 might be a specific gateway node for a SaaS provider (such as an AWS CloudFront edge location or an Office 365 endpoint) used by these scheduled jobs. During peak backup windows, the high frequency of requests can trigger the rule despite the traffic being benign and expected.