This hypothesis targets potential web-based initial access or command-and-control channels by identifying traffic to known malicious URLs associated with the 176-9-104-142 tag, which adversaries often use to deliver payloads or exfiltrate data. Proactively hunting for these indicators in Azure Sentinel allows the SOC to detect compromised endpoints or lateral movement attempts before they escalate into a full breach, leveraging URL reputation data to surface hidden threats in network logs.
Threat: 176-9-104-142 Total URLs: 2 Active URLs: 0
| URL | Status | Threat | Date Added |
|---|---|---|---|
hxxp://176.9.104.142/bin.sh | offline | malware_download | 2026-09-11 |
hxxp://176.9.104.142/ohshit.sh | offline | malware_download | 2026-09-11 |
// Hunt for DNS resolution of URLhaus malicious domains
// Threat: 176-9-104-142
let malicious_domains = dynamic(["176.9.104.142"]);
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(["176.9.104.142"]);
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 |
176.9.104.142 for status pings or license validation.
10.20.5.0/24) or exclude the specific user agent string associated with the legacy app’s health check script (e.g., LegacyApp-HealthCheck/1.0).cron on Linux or Task Scheduler on Windows) that runs a script to verify backup integrity by fetching a checksum or status file from a remote storage endpoint hosted at 176.9.104.142.
443 (HTTPS) and the source process is a known backup utility (e.g., veeamagent.exe, commvaultclient.exe, or python.exe running a specific backup script path).176.9.104.142 during a build step.
192.168.100.0/24) and correlate with active pipeline job IDs or exclude if the User-Agent contains Jenkins or GitLab-Runner.