This hypothesis targets potential initial access or command-and-control activity by identifying user interactions with 14 known malicious URLs associated with the IP 64.89.160.48. Proactively hunting for these specific indicators in Azure Sentinel allows the SOC to detect compromised endpoints or phishing campaigns before they escalate into lateral movement or data exfiltration events.
Threat: 64-89-160-48 Total URLs: 14 Active URLs: 14
| URL | Status | Threat | Date Added |
|---|---|---|---|
hxxp://64.89.160.48/pm68k | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/parm5 | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/cat.sh | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/bins/cat.sh | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/parm | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/pmips | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/parm7 | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/px86 | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/psh4 | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/pspc | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/pmpsl | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/parm6 | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/bins/pppc | online | malware_download | 2026-09-27 |
hxxp://64.89.160.48/pppc | online | malware_download | 2026-09-27 |
// Hunt for DNS resolution of URLhaus malicious domains
// Threat: 64-89-160-48
let malicious_domains = dynamic(["64.89.160.48"]);
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(["64.89.160.48"]);
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 |
Legacy Application Health Checks: A legacy Java-based ERP system (e.g., SAP NetWeaver or Oracle EBS) running on a Windows Server 2016 host executes a scheduled curl or wget command to ping a specific health-check endpoint hosted on the 64-89-160-48 IP range for failover verification.
java.exe or curl.exe originating from the C:\Program Files\Java\ or C:\SAP\ directories when the destination URL matches the specific known-good path (e.g., /healthcheck) rather than a generic root or suspicious path.CI/CD Pipeline Artifact Download: An Azure DevOps or Jenkins agent on a build server downloads a dependency package or container image layer from a private registry mirror that happens to be hosted on the 64-89-160-48 IP. The agent process (jenkins-agent.exe or docker.exe) initiates the HTTPS connection.
jenkins-agent.exe, docker.exe, kubectl.exe) where the User-Agent header contains Jenkins or Docker and the source port is ephemeral, provided the destination path includes /v2/ or /api/.Internal Monitoring Agent Polling: A Datadog or New Relic monitoring agent installed on a web server polls a custom metrics endpoint that is reverse-proxied to the 64-89-160-48 IP for internal telemetry ingestion. The agent process (agent.exe or newrelic-agent.exe) makes frequent, short-lived HTTPS requests.