ThreatFox: PureRAT IOCs | SOC Hunt Feed

Hunt Hypothesis

This hunt detects adversary activity involving the deployment of PureRAT remote access trojans by monitoring network and endpoint telemetry against a curated set of 35 specific Indicators of Compromise (IOCs). Proactive hunting for these signatures in Azure Sentinel is critical to identify early-stage lateral movement and command-and-control communications that may bypass standard signature-based detections, thereby reducing dwell time for this high-severity threat.

IOC Summary

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

Type	Value	Threat Type	First Seen	Confidence
ip:port	`84[.]201[.]20[.]74:443`	botnet_cc	2026-07-29	75%
ip:port	`193[.]233[.]198[.]62:56003`	botnet_cc	2026-07-29	75%
ip:port	`167[.]148[.]41[.]137:56001`	botnet_cc	2026-07-29	75%
ip:port	`15[.]235[.]151[.]49:56001`	botnet_cc	2026-07-29	75%
ip:port	`15[.]235[.]151[.]49:56002`	botnet_cc	2026-07-29	75%
ip:port	`15[.]235[.]151[.]49:56003`	botnet_cc	2026-07-29	75%
ip:port	`94[.]26[.]3[.]166:443`	botnet_cc	2026-07-29	75%
ip:port	`93[.]152[.]221[.]67:443`	botnet_cc	2026-07-29	75%
ip:port	`94[.]154[.]32[.]252:443`	botnet_cc	2026-07-29	75%
ip:port	`91[.]92[.]40[.]56:9267`	botnet_cc	2026-07-29	75%
ip:port	`89[.]213[.]118[.]63:443`	botnet_cc	2026-07-29	75%
ip:port	`64[.]224[.]17[.]110:443`	botnet_cc	2026-07-29	75%
ip:port	`51[.]79[.]185[.]253:443`	botnet_cc	2026-07-29	75%
ip:port	`5[.]253[.]86[.]251:443`	botnet_cc	2026-07-29	75%
ip:port	`45[.]89[.]48[.]12:56001`	botnet_cc	2026-07-29	75%
ip:port	`45[.]89[.]48[.]12:56002`	botnet_cc	2026-07-29	75%
ip:port	`45[.]89[.]48[.]12:56003`	botnet_cc	2026-07-29	75%
ip:port	`45[.]192[.]211[.]63:56003`	botnet_cc	2026-07-29	75%
ip:port	`45[.]157[.]233[.]124:56001`	botnet_cc	2026-07-29	75%
ip:port	`45[.]157[.]233[.]124:56002`	botnet_cc	2026-07-29	75%
ip:port	`45[.]157[.]233[.]124:56003`	botnet_cc	2026-07-29	75%
ip:port	`45[.]153[.]34[.]203:443`	botnet_cc	2026-07-29	75%
ip:port	`27[.]124[.]36[.]151:443`	botnet_cc	2026-07-29	75%
ip:port	`27[.]124[.]36[.]136:443`	botnet_cc	2026-07-29	75%
ip:port	`217[.]156[.]122[.]76:443`	botnet_cc	2026-07-29	75%

KQL: Ip Hunt

// Hunt for network connections to known malicious IPs
// Source: ThreatFox - PureRAT
let malicious_ips = dynamic(["84.201.20.74", "192.229.115.162", "45.157.233.124", "91.92.40.56", "167.148.41.137", "64.224.17.110", "94.26.3.166", "217.156.122.76", "217.60.195.167", "94.154.32.252", "185.247.208.91", "27.124.36.136", "5.253.86.251", "93.152.221.67", "192.229.115.156", "45.192.211.63", "15.235.151.49", "45.89.48.12", "193.164.5.4", "193.233.198.62", "89.213.118.63", "192.229.115.154", "194.9.6.82", "27.124.36.151", "217.60.195.153", "209.99.190.23", "45.153.34.203", "51.79.185.253"]);
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(["84.201.20.74", "192.229.115.162", "45.157.233.124", "91.92.40.56", "167.148.41.137", "64.224.17.110", "94.26.3.166", "217.156.122.76", "217.60.195.167", "94.154.32.252", "185.247.208.91", "27.124.36.136", "5.253.86.251", "93.152.221.67", "192.229.115.156", "45.192.211.63", "15.235.151.49", "45.89.48.12", "193.164.5.4", "193.233.198.62", "89.213.118.63", "192.229.115.154", "194.9.6.82", "27.124.36.151", "217.60.195.153", "209.99.190.23", "45.153.34.203", "51.79.185.253"]);
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 specific false positive scenarios for the ThreatFox: PureRAT IOCs detection rule, along with suggested filters and exclusions tailored for an enterprise environment:

Scenario: Automated Software Deployment via SCCM/Intune
- Context: The IT Operations team uses Microsoft Endpoint Configuration Manager (SCCM) or Intune to push a new version of the “PureRAT” remote access utility to all workstations during a scheduled maintenance window. This triggers the detection as the installer executes and registers known IOCs (hashes, file paths, registry keys) associated with PureRAT.
- Filter/Exclusion: Create an exclusion based on the process image path C:\Windows\CCM\Setup\ or C:\Program Files (x86)\Microsoft Intune Agent\. Additionally, filter alerts where the parent process is ccmsetup.exe or IntuneManagementExtension.exe and the event occurs within the defined maintenance window (e.g., 02:00–04:00 UTC).
Scenario: Scheduled Backup Jobs Utilizing Remote Access
- Context: A nightly backup job configured in Veeam or Commvault utilizes PureRAT as a transport agent to establish secure connections between the backup server and remote endpoints. The scheduled task triggers the PureRAT service, generating network traffic and file access patterns that match the 35 IOCs in the hunt package.
- Filter/Exclusion: Exclude alerts where the initiating process is VeeamBackupService.exe or vcagent.exe. Implement a logic filter to suppress detections if the source IP belongs to the internal backup subnet (e.g., 10.20.30.0/24) and the destination port matches the standard PureRAT communication ports defined in the rule.
**Scenario: Helpdesk