ThreatFox: PureRAT IOCs | SOC Hunt Feed

Hunt Hypothesis

This hunt detects adversary activity involving the PureRAT remote access trojan by monitoring for matches against a curated set of 55 specific indicators of compromise (IOCs). Proactively hunting for these signals in Azure Sentinel is critical to identify early-stage PureRAT infections that may evade standard signature-based defenses, thereby preventing potential data exfiltration and lateral movement.

IOC Summary

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

Type	Value	Threat Type	First Seen	Confidence
ip:port	`51[.]79[.]185[.]253:56003`	botnet_cc	2026-07-30	75%
ip:port	`50[.]114[.]184[.]63:444`	botnet_cc	2026-07-30	75%
ip:port	`50[.]114[.]184[.]63:442`	botnet_cc	2026-07-30	75%
ip:port	`27[.]124[.]36[.]151:56002`	botnet_cc	2026-07-30	75%
ip:port	`209[.]99[.]190[.]23:45001`	botnet_cc	2026-07-30	75%
ip:port	`176[.]65[.]148[.]198:7777`	botnet_cc	2026-07-30	75%
ip:port	`103[.]148[.]58[.]8:56003`	botnet_cc	2026-07-30	75%
ip:port	`222[.]167[.]208[.]153:56003`	botnet_cc	2026-07-30	75%
ip:port	`209[.]99[.]184[.]15:55006`	botnet_cc	2026-07-30	75%
ip:port	`31[.]77[.]57[.]7:56002`	botnet_cc	2026-07-30	75%
ip:port	`31[.]77[.]57[.]7:56001`	botnet_cc	2026-07-30	75%
ip:port	`31[.]77[.]57[.]7:56003`	botnet_cc	2026-07-30	75%
ip:port	`172[.]81[.]133[.]197:56002`	botnet_cc	2026-07-30	75%
ip:port	`172[.]93[.]212[.]254:56001`	botnet_cc	2026-07-30	75%
ip:port	`144[.]172[.]106[.]142:1337`	botnet_cc	2026-07-30	75%
ip:port	`157[.]254[.]194[.]144:56003`	botnet_cc	2026-07-30	75%
ip:port	`157[.]254[.]194[.]144:56001`	botnet_cc	2026-07-30	75%
ip:port	`217[.]217[.]97[.]187:8080`	botnet_cc	2026-07-30	75%
ip:port	`185[.]100[.]157[.]93:56002`	botnet_cc	2026-07-30	75%
ip:port	`185[.]100[.]157[.]93:56001`	botnet_cc	2026-07-30	75%
ip:port	`206[.]245[.]165[.]24:56003`	botnet_cc	2026-07-30	75%
ip:port	`206[.]245[.]165[.]24:56001`	botnet_cc	2026-07-30	75%
ip:port	`206[.]245[.]165[.]24:56002`	botnet_cc	2026-07-30	75%
ip:port	`138[.]255[.]160[.]203:56003`	botnet_cc	2026-07-30	75%
ip:port	`172[.]93[.]212[.]218:56001`	botnet_cc	2026-07-30	75%

KQL: Ip Hunt

// Hunt for network connections to known malicious IPs
// Source: ThreatFox - PureRAT
let malicious_ips = dynamic(["168.222.97.151", "173.208.180.138", "185.100.157.93", "23.111.14.80", "192.3.42.138", "172.94.9.25", "198.135.55.89", "85.11.167.61", "144.172.106.142", "31.77.57.7", "176.65.148.198", "147.124.203.21", "184.174.20.138", "27.124.36.151", "50.114.184.63", "188.209.158.220", "195.177.94.109", "157.254.194.144", "209.99.184.15", "217.217.97.187", "51.79.185.253", "151.247.22.50", "209.99.190.23", "172.81.133.197", "206.245.165.24", "172.93.212.254", "103.148.58.8", "82.38.44.188", "138.255.160.203", "222.167.208.153", "103.148.58.10", "172.93.212.218", "108.174.56.175", "82.22.7.20"]);
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(["168.222.97.151", "173.208.180.138", "185.100.157.93", "23.111.14.80", "192.3.42.138", "172.94.9.25", "198.135.55.89", "85.11.167.61", "144.172.106.142", "31.77.57.7", "176.65.148.198", "147.124.203.21", "184.174.20.138", "27.124.36.151", "50.114.184.63", "188.209.158.220", "195.177.94.109", "157.254.194.144", "209.99.184.15", "217.217.97.187", "51.79.185.253", "151.247.22.50", "209.99.190.23", "172.81.133.197", "206.245.165.24", "172.93.212.254", "103.148.58.8", "82.38.44.188", "138.255.160.203", "222.167.208.153", "103.148.58.10", "172.93.212.218", "108.174.56.175", "82.22.7.20"]);
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: Endpoint Management Agent Communication
- Context: Enterprise endpoint protection suites (e.g., CrowdStrike Falcon, Microsoft Defender for Endpoint, or Carbon Black) frequently communicate with their cloud management consoles using specific IP ranges. If the PureRAT IOCs include IPs that overlap with these vendor backbones, legitimate telemetry uploads will trigger alerts.
- Suggested Filter/Exclusion: Create a whitelist exclusion based on the Process Name (e.g., C:\Program Files\CrowdStrike\fsquint.exe) and exclude traffic to known vendor IP ranges defined in your network topology documentation.
Scenario: Scheduled Patch Deployment Jobs
- Context: During nightly maintenance windows, automated patching tools like WSUS (Windows Server Update Services) or SCCM/MECM initiate connections to external update repositories. If PureRAT IOCs match the IP addresses of Microsoft Update servers or third-party software vendors used by the organization, these scheduled jobs will generate high-volume false positives.
- Suggested Filter/Exclusion: Implement a time-based filter that suppresses alerts for this rule between 01:00 and 05:00 local time on weekdays, specifically excluding processes initiated by wuauserv.exe or the SCCM agent (ccmexec.exe).
Scenario: Cloud Backup and Synchronization Services
- Context: Business continuity tools such as Veeam, Rubrik, or OneDrive for Business maintain persistent connections to cloud storage endpoints. If PureRAT IOCs include generic cloud infrastructure IPs (e.g., AWS, Azure, or Google Cloud ranges) that these