ThreatFox: Unknown Loader IOCs

Hunt Hypothesis

This detection identifies adversary behavior where unknown loader processes execute suspicious input/output operations indicative of initial command-and-control communication or payload staging. Proactively hunting for these indicators in Azure Sentinel is critical to uncover stealthy threats that may bypass standard signature-based defenses by leveraging the platform’s ability to correlate real-time telemetry with emerging ThreatFox intelligence feeds.

IOC Summary

Malware Family: Unknown Loader Total IOCs: 2 IOC Types: domain

KQL: Domain Hunt

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

Required Data Sources

References

• ThreatFox — Unknown Loader

False Positive Guidance

Here are 4 specific false positive scenarios for the ThreatFox: Unknown Loader IOCs rule, tailored for a legitimate enterprise environment:

• Scenario: Enterprise Software Deployment via SCCM/Intune

  • Context: During scheduled maintenance windows, System Center Configuration Manager (SCCM) or Microsoft Intune deploys new applications to endpoints. These deployments often utilize temporary loader scripts (e.g., msiexec.exe spawning a transient setup_loader.exe) that execute from the %TEMP% directory before moving files to the Program Files folder. The rule flags these transient loaders as “Unknown” because they lack established reputation in the ThreatFox database yet are part of an authorized deployment pipeline.
  • Filter/Exclusion: Exclude process paths containing C:\Windows\CCM\, C:\ProgramData\Microsoft\IntuneManagementExtension\, or parent processes named ccmexec.exe and Microsoft.Intune.Management.Extension.exe. Additionally, create a whitelist for file hashes associated with known deployment packages.

• Scenario: Automated Patch Management Execution

  • Context: Third-party patch management solutions like Ivanti Endpoint Manager or ManageEngine Patch Manager Plus frequently download and execute temporary loader binaries to verify integrity before applying updates. These loaders often run as scheduled tasks under the SYSTEM or a dedicated service account (e.g., svc-patchagent). The detection logic triggers because these dynamic, version-specific loader executables are generated daily and may not yet be indexed in the global ThreatFox IOC feed.
  • Filter/Exclusion: Filter out events where the parent process is TaskScheduler (svchost.exe) or specific patch management agents (e.g., IvantiAgent.exe, PatchManagerService.exe). Implement a rule to ignore IOCs originating from the C:\ProgramData\Ivanti\ and