← Back to SOC feed Coverage →

ThreatFox: IceRat IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
backdooriocjar-iceratthreatfox
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-08-25T23:00:00Z · Confidence: high

Hunt Hypothesis

This hunt detects adversary activity involving specific indicators of compromise (IOCs) linked to the IceRat remote access tool, which is frequently utilized by threat actors for command and control operations. A SOC team should proactively search for these IOCs in Azure Sentinel to identify early-stage infections or lateral movement attempts that may have evaded standard signature-based detections.

IOC Summary

Malware Family: IceRat Total IOCs: 3 IOC Types: sha1_hash, md5_hash, sha256_hash

TypeValueThreat TypeFirst SeenConfidence
sha256_hash35daec4729842b66099ddbbe4bd1bc21240628d38f0e54a84b80d1fd11d2f1afpayload2026-08-2595%
sha1_hash83e1cffed0bad229afac9c8fa285173d6f07dbc1payload2026-08-2595%
md5_hashd4a19a109b091d66e0930bd553256b1bpayload2026-08-2595%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - IceRat
let malicious_hashes = dynamic(["35daec4729842b66099ddbbe4bd1bc21240628d38f0e54a84b80d1fd11d2f1af", "83e1cffed0bad229afac9c8fa285173d6f07dbc1", "d4a19a109b091d66e0930bd553256b1b"]);
DeviceFileEvents
| where SHA256 in (malicious_hashes) or SHA1 in (malicious_hashes) or MD5 in (malicious_hashes)
| project Timestamp, DeviceName, FileName, FolderPath, SHA256, InitiatingProcessFileName
| order by Timestamp desc

Required Data Sources

Sentinel TableNotes
DeviceFileEventsEnsure this data connector is enabled

References

False Positive Guidance

Original source: https://threatfox.abuse.ch/browse/malware/jar.icerat/