← Back to SOC feed Coverage →

ThreatFox: MASS Logger IOCs

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

Hunt Hypothesis

The ThreatFox: MASS Logger IOCs rule detects potential command and control communication associated with the MASS Logger malware, which is commonly used for data exfiltration and persistence. SOC teams should proactively hunt for this behavior in Azure Sentinel to identify and mitigate advanced persistent threats leveraging known malicious IOCs before they cause significant data loss or system compromise.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hashfb5a09899b06e4ed91b14a9e67f5ece2a558a877payload2026-06-1195%
md5_hash0ff94617c08fe032327753b286011da5payload2026-06-1195%
sha256_hash574c4503c071e8e8892d267e786acdf811970d4f927cf4536a870c8ba2fc7a13payload2026-06-1195%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - MASS Logger
let malicious_hashes = dynamic(["fb5a09899b06e4ed91b14a9e67f5ece2a558a877", "0ff94617c08fe032327753b286011da5", "574c4503c071e8e8892d267e786acdf811970d4f927cf4536a870c8ba2fc7a13"]);
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.masslogger/