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

Hunt Hypothesis

This hypothesis targets the presence of known IOCs associated with the GCleaner malware, which is frequently deployed to establish persistence and execute malicious payloads on compromised endpoints. Proactively hunting for these indicators in Azure Sentinel allows the SOC team to identify and isolate infected assets before the adversary can leverage the malware for lateral movement or data exfiltration.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
md5_hash29a971dac08fc3014072ef2c7e4c8758payload2026-09-0495%
sha256_hash6719c071c7e08af59b520f5ca22f77e11e4a47d7d5e411f50e523f670d656495payload2026-09-0495%
sha1_hash9f22d44425c9425ae131332735f05502edcc1f12payload2026-09-0495%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - GCleaner
let malicious_hashes = dynamic(["29a971dac08fc3014072ef2c7e4c8758", "6719c071c7e08af59b520f5ca22f77e11e4a47d7d5e411f50e523f670d656495", "9f22d44425c9425ae131332735f05502edcc1f12"]);
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/win.gcleaner/