← Back to SOC feed Coverage →

ThreatFox: Logedrut IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
iocthreatfoxwin-logedrut
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 Logedrut indicators of compromise, which are frequently used by threat actors to establish persistence and execute malicious payloads within Azure environments. Proactively hunting for these IOCs allows the SOC team to identify compromised assets early, mitigating the risk of lateral movement and data exfiltration associated with this high-severity threat.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha256_hashc13cea04f598e2b0c248d603a6e31bd13aabb64d8149c1b6a77b64e0b983a86fpayload2026-09-2495%
sha1_hashf495880eb6ee7bb930a9957f092f395695cf89a4payload2026-09-2495%
md5_hash833cdd365d2dd29832a711dc2da5a584payload2026-09-2495%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - Logedrut
let malicious_hashes = dynamic(["c13cea04f598e2b0c248d603a6e31bd13aabb64d8149c1b6a77b64e0b983a86f", "f495880eb6ee7bb930a9957f092f395695cf89a4", "833cdd365d2dd29832a711dc2da5a584"]);
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.logedrut/