← 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-05T23:00:00Z · Confidence: high

Hunt Hypothesis

This hunt targets adversary behavior involving the execution of known malicious indicators from the GCleaner campaign to identify potential compromise within the environment. Proactively hunting for these specific IOCs in Azure Sentinel is critical because early detection allows the SOC team to isolate affected assets before the malware can establish persistence or exfiltrate sensitive data.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hashfb1566a75cbb2034b53b31474ab4d21a7caea50epayload2026-07-0595%
md5_hash27af4194b3fb1179eca9bb2ebd511a12payload2026-07-0595%
sha256_hash65736a4315b49718b68e1a72d24ff61e1b0537f2c2deb19f5bb339f2aa10e459payload2026-07-0595%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - GCleaner
let malicious_hashes = dynamic(["fb1566a75cbb2034b53b31474ab4d21a7caea50e", "27af4194b3fb1179eca9bb2ebd511a12", "65736a4315b49718b68e1a72d24ff61e1b0537f2c2deb19f5bb339f2aa10e459"]);
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 and corresponding exclusion strategies for the ThreatFox: GCleaner IOCs detection rule in an enterprise environment:

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