This hunt detects adversary behavior involving the consumption of newly identified malicious URLs associated with IP address 192.253.248.52, which are flagged by URLhaus as indicators of potential web-based threats or command-and-control infrastructure. The SOC team should proactively hunt for these specific URLs in Azure Sentinel to rapidly identify early-stage compromise events and mitigate risks before they escalate into broader lateral movement or data exfiltration incidents.
Threat: 192-253-248-52 Total URLs: 2 Active URLs: 2
| URL | Status | Threat | Date Added |
|---|---|---|---|
hxxps://192.253.248.52/dl | online | malware_download | 2026-08-31 |
hxxps://192.253.248.52/get | online | malware_download | 2026-08-31 |
// Hunt for DNS resolution of URLhaus malicious domains
// Threat: 192-253-248-52
let malicious_domains = dynamic(["192.253.248.52"]);
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.253.248.52"]);
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: 192-253-248-52 Malicious URLs detection rule, along with targeted filtering strategies:
Scenario: Automated Security Tool Telemetry & Updates
192.253.248.52 (often associated with URLhaus feeds) to download threat intelligence updates, signature definitions, or submit telemetry data.C:\Program Files\CrowdStrike\csfalcon.exe and C:\Windows\System32\MsMpEng.exe when the destination IP is 192.253.248-52.Scenario: Scheduled Cloud Backup & Synchronization Jobs
svc-veeam-backup) between 01:00 and 05:00 daily, or exclude specific scheduled task IDs known to trigger these connections.Scenario: Third-Party SaaS Integration & API Polling