← Back to SOC feed Coverage →

ThreatFox: GCleaner IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
iocthreatfoxwin-gcleaner
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-10T23:00:00Z · Confidence: high

Hunt Hypothesis

This hunt detects adversary behavior involving the execution of known malicious indicators from the GCleaner campaign, which typically target endpoints to establish persistence and exfiltrate sensitive data. Proactively hunting for these specific IOCs in Azure Sentinel is critical because early identification allows the SOC team to isolate compromised assets before the malware can propagate laterally across the cloud infrastructure.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha256_hash7197e9097b977d138f3856a8aca3a3b3c6b28b82cc76a3667ef1364e820195cbpayload2026-07-1095%
sha1_hashcaceab5925bfda9eac39d24585f42db05071f531payload2026-07-1095%
md5_hash845a1bc9408c542cf748ba647c2e680epayload2026-07-1095%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - GCleaner
let malicious_hashes = dynamic(["7197e9097b977d138f3856a8aca3a3b3c6b28b82cc76a3667ef1364e820195cb", "caceab5925bfda9eac39d24585f42db05071f531", "845a1bc9408c542cf748ba647c2e680e"]);
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

Here are specific false positive scenarios for the ThreatFox: GCleaner IOCs detection rule, tailored for an enterprise environment:

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