← Back to SOC feed Coverage →

ThreatFox: GUIDLOADER IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
iocthreatfoxwin-guidloader
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-11T11:00:00Z · Confidence: high

Hunt Hypothesis

This hunt targets the presence of specific IOCs associated with the GUIDLOADER malware, which adversaries deploy to establish persistence and execute payloads within the environment. Proactively hunting for these indicators in Azure Sentinel allows the SOC team to identify compromised assets early, potentially disrupting the attacker’s post-exploitation activities before they escalate privileges or exfiltrate data.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
md5_hash3a0e80415e7e1f49ee3bd7912832f3c0payload2026-09-1195%
sha256_hash51484aa565b674d5b92d1cccb0f8d86378c1c40ee3b321d2f6b5e192af200458payload2026-09-1195%
sha1_hashb3233de7e91adf25c6dddecdaffc1eb6d2e6b43bpayload2026-09-1195%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - GUIDLOADER
let malicious_hashes = dynamic(["3a0e80415e7e1f49ee3bd7912832f3c0", "51484aa565b674d5b92d1cccb0f8d86378c1c40ee3b321d2f6b5e192af200458", "b3233de7e91adf25c6dddecdaffc1eb6d2e6b43b"]);
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.guidloader/