← Back to SOC feed Coverage →

ThreatFox: Remcos IOCs

ioc-hunt HIGH ThreatFox
CommonSecurityLogDeviceNetworkEventsDnsEvents
iocthreatfoxwin-remcos
This rule was pulled from an open-source repository and enriched with AI. Validate in a test environment before deploying to production.
View original rule at ThreatFox →
Retrieved: 2026-07-10T11:00:01Z · Confidence: high

Hunt Hypothesis

This hunt targets adversary behavior characterized by the presence of specific Indicators of Compromise (IOCs) linked to the Remcos remote access trojan, which often establishes persistence and exfiltrates sensitive data from compromised endpoints. Proactively hunting for these signatures in Azure Sentinel is critical because early detection of Remcos activity allows the SOC team to isolate infected assets before the malware can expand its lateral movement or establish long-term command-and-control channels within the cloud environment.

IOC Summary

Malware Family: Remcos Total IOCs: 11 IOC Types: domain, ip:port

TypeValueThreat TypeFirst SeenConfidence
ip:port94[.]199[.]45[.]148:443botnet_cc2026-07-1075%
ip:port85[.]206[.]168[.]238:26076botnet_cc2026-07-1075%
ip:port45[.]74[.]7[.]195:8015botnet_cc2026-07-1075%
ip:port20[.]204[.]61[.]204:21891botnet_cc2026-07-1075%
ip:port155[.]103[.]69[.]30:14647botnet_cc2026-07-1075%
ip:port13[.]73[.]107[.]136:443botnet_cc2026-07-1075%
domainanubixfreedom001.duckdns.orgbotnet_cc2026-07-1075%
ip:port102[.]220[.]160[.]125:56793botnet_cc2026-07-10100%
ip:port172[.]111[.]163[.]176:65070botnet_cc2026-07-10100%
ip:port172[.]111[.]225[.]72:56090botnet_cc2026-07-10100%
ip:port198[.]135[.]51[.]238:2404botnet_cc2026-07-10100%

KQL: Ip Hunt

// Hunt for network connections to known malicious IPs
// Source: ThreatFox - Remcos
let malicious_ips = dynamic(["198.135.51.238", "102.220.160.125", "85.206.168.238", "155.103.69.30", "13.73.107.136", "20.204.61.204", "94.199.45.148", "172.111.163.176", "172.111.225.72", "45.74.7.195"]);
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(["198.135.51.238", "102.220.160.125", "85.206.168.238", "155.103.69.30", "13.73.107.136", "20.204.61.204", "94.199.45.148", "172.111.163.176", "172.111.225.72", "45.74.7.195"]);
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 - Remcos
let malicious_domains = dynamic(["anubixfreedom001.duckdns.org"]);
DnsEvents
| where Name has_any (malicious_domains)
| project TimeGenerated, Computer, Name, IPAddresses, QueryType
| order by TimeGenerated desc

Required Data Sources

Sentinel TableNotes
CommonSecurityLogEnsure this data connector is enabled
DeviceNetworkEventsEnsure this data connector is enabled
DnsEventsEnsure this data connector is enabled

References

False Positive Guidance

Here are 4 specific false positive scenarios for the ThreatFox: Remcos IOCs detection rule in an enterprise environment, along with suggested filters or exclusions:

Original source: https://threatfox.abuse.ch/browse/malware/win.remcos/