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

Hunt Hypothesis

This detection identifies adversary activity linked to the GCleaner malware by monitoring specific Indicators of Compromise (IOCs) known to facilitate its initial infection and persistence mechanisms within Azure Sentinel. Proactive hunting for these IOCs is critical because early identification allows the SOC team to rapidly isolate affected endpoints, preventing lateral movement and potential data exfiltration before the threat escalates.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hash3941abf37772bfdeefa1d8b8bc617f9e1ce4bd48payload2026-08-2895%
md5_hash801e7911d8ef33ab7843bb638c0b5abcpayload2026-08-2895%
sha256_hashc496e8e8f7cc2e40c515c9dbd98ffce43861acaf504466f478ceaebf712214b8payload2026-08-2895%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - GCleaner
let malicious_hashes = dynamic(["3941abf37772bfdeefa1d8b8bc617f9e1ce4bd48", "801e7911d8ef33ab7843bb638c0b5abc", "c496e8e8f7cc2e40c515c9dbd98ffce43861acaf504466f478ceaebf712214b8"]);
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 filters for the ThreatFox: GCleaner IOCs detection rule in an enterprise environment:

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