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

Hunt Hypothesis

This hypothesis targets the presence of known indicators of compromise associated with the GCleaner malware, which often leverages fileless or in-memory techniques to establish persistence on Azure-hosted workloads. Proactively hunting for these IOCs allows the SOC team to identify early-stage infections before the adversary can execute lateral movement or data exfiltration within the Azure environment.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
md5_hash55d635733571cf404f3af64646dc97e9payload2026-09-2495%
sha256_hashce3d16f1bcb319135a99b10d4daa2a680c2cadadb8d8082b39d3696b7016e096payload2026-09-2495%
sha1_hash668dd8566eacd7b89dab013b36cccf0f94be8c4apayload2026-09-2495%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - GCleaner
let malicious_hashes = dynamic(["55d635733571cf404f3af64646dc97e9", "ce3d16f1bcb319135a99b10d4daa2a680c2cadadb8d8082b39d3696b7016e096", "668dd8566eacd7b89dab013b36cccf0f94be8c4a"]);
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/