ThreatFox: PureRAT IOCs | SOC Hunt Feed

Hunt Hypothesis

This hunt detects adversary behavior involving the deployment of PureRAT remote access tools by monitoring for specific indicators of compromise such as malicious hashes and network connections. A SOC team should proactively hunt for these IOCs in Azure Sentinel to identify early-stage reconnaissance or command-and-control activities that could lead to data exfiltration or lateral movement within the enterprise environment.

IOC Summary

Malware Family: PureRAT Total IOCs: 3 IOC Types: ip:port

Type	Value	Threat Type	First Seen	Confidence
ip:port	`104[.]249[.]10[.]122:56001`	botnet_cc	2026-07-23	75%
ip:port	`104[.]249[.]10[.]122:56002`	botnet_cc	2026-07-23	75%
ip:port	`104[.]249[.]10[.]122:56003`	botnet_cc	2026-07-23	75%

KQL: Ip Hunt

// Hunt for network connections to known malicious IPs
// Source: ThreatFox - PureRAT
let malicious_ips = dynamic(["104.249.10.122"]);
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(["104.249.10.122"]);
DeviceNetworkEvents
| where RemoteIP in (malicious_ips)
| project Timestamp, DeviceName, RemoteIP, RemotePort, InitiatingProcessFileName, ActionType
| order by Timestamp desc

Required Data Sources

Sentinel Table	Notes
`CommonSecurityLog`	Ensure this data connector is enabled
`DeviceNetworkEvents`	Ensure this data connector is enabled

References

ThreatFox — PureRAT

False Positive Guidance

Here are 4 specific false positive scenarios for the ThreatFox: PureRAT IOCs detection rule, including suggested filters and exclusions tailored for an enterprise environment:

Scenario: Enterprise Endpoint Protection Scans
- Context: Security agents like CrowdStrike Falcon, Microsoft Defender for Endpoint (MDE), or SentinelOne frequently download threat intelligence feeds or perform local signature updates. These processes often generate network connections to known PureRAT C2 infrastructure IPs or hash signatures that match the rule’s IOCs, particularly during off-hours maintenance windows.
- Filter/Exclusion: Create a suppression rule excluding traffic originating from specific service accounts (e.g., svc-crowdstrike, mdefender-updater) and limiting matches to the “Application” field where the executable path contains \Program Files\ or \Windows\System32\.
Scenario: Scheduled RMM and Patch Management Jobs
- Context: Remote Monitoring and Management (RMM) tools such as ManageEngine Desktop Central, PDQ Deploy, or SCCM (Configuration Manager) often utilize shared libraries or dependencies that include PureRAT components for remote command execution. A nightly patch deployment job might trigger a connection to an IOC associated with the PureRAT framework while pushing updates to 50+ workstations simultaneously.
- Filter/Exclusion: Exclude alerts where the source process is identified as wuauserv.exe, ccmexec.exe (SCCM), or specific RMM agent executables, and restrict the alert window to exclude standard maintenance windows (e.g., 02:00–04:00 local time).
Scenario: Legitimate Third-Party Software Installations
- Context: The deployment of legitimate software suites such as Adobe Creative Cloud, Zoom Enterprise,