ThreatFox: IClickFix IOCs

Hunt Hypothesis

This hunt detects adversary activity involving known indicators of compromise (IOCs) from the ThreatFox intelligence feed specifically linked to the IClickFix platform, which may signal unauthorized access or malicious reconnaissance within the organization’s ecosystem. SOC teams should proactively hunt for these signals in Azure Sentinel because early identification of these high-severity IOCs allows for rapid containment of potential threats before they escalate into broader data breaches or service disruptions.

IOC Summary

Malware Family: IClickFix Total IOCs: 2 IOC Types: ip:port, domain

KQL: Ip Hunt

// Hunt for network connections to known malicious IPs
// Source: ThreatFox - IClickFix
let malicious_ips = dynamic(["85.239.149.16"]);
CommonSecurityLog
| where DestinationIP in (malicious_ips) or SourceIP in (malicious_ips)
| project TimeGenerated, SourceIP, DestinationIP, DestinationPort, DeviceAction, Activity
| order by TimeGenerated desc

KQL: Ip Hunt Device

// Hunt in Defender for Endpoint network events
let malicious_ips = dynamic(["85.239.149.16"]);
DeviceNetworkEvents
| where RemoteIP in (malicious_ips)
| project Timestamp, DeviceName, RemoteIP, RemotePort, InitiatingProcessFileName, ActionType
| order by Timestamp desc

KQL: Domain Hunt

// Hunt for DNS queries to known malicious domains
// Source: ThreatFox - IClickFix
let malicious_domains = dynamic(["royalensemble.com"]);
DnsEvents
| where Name has_any (malicious_domains)
| project TimeGenerated, Computer, Name, IPAddresses, QueryType
| order by TimeGenerated desc

Required Data Sources

References

• ThreatFox — IClickFix

False Positive Guidance

Here are specific false positive scenarios and corresponding filters for the ThreatFox: IClickFix IOCs detection rule:

• Scheduled Helpdesk Ticket Sync Job

  • Scenario: The enterprise runs a nightly PowerShell script (SyncHelpDeskData.ps1) on the SVC-ITSM server to synchronize ticket metadata with the IClickFix platform. This job establishes outbound HTTPS connections to known IClickFix API endpoints, triggering the IOC match.
  • Filter/Exclusion: Exclude traffic originating from the specific service account svc-itmsync running on host SVC-ITSM, provided the destination IP is within the approved IClickFix CIDR range and the process path matches C:\Scripts\SyncHelpDeskData.ps1.

• Endpoint Security Agent Integration

  • Scenario: The organization uses Microsoft Defender for Endpoint (MDE) or CrowdStrike Falcon agents configured to push real-time telemetry to IClickFix for automated incident creation. The agent’s background service (DefenderService.exe or FalconSensor.exe) periodically queries the IClickFix API, generating network logs that match the rule’s IOCs.
  • Filter/Exclusion: Create an exclusion based on the process image path (e.g., C:\Program Files\Microsoft Defender\MsMpEng.exe) and restrict it to allow connections only from the “Endpoint Management” security group to IClickFix FQDNs.

• ITSM Admin Dashboard Refresh

  • Scenario: During business hours, IT administrators access the IClickFix web portal via a corporate browser (e.g., Chrome or Edge) on their workstations (WS-ADMIN-01 through WS-ADMIN-50). The browser’s background processes frequently fetch assets and configuration data from IClickFix servers, triggering the detection.
  • **Filter/Ex