← Back to SOC feed Coverage →

ThreatFox: stealler IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
iocpy-steallerthreatfox
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-06T11:00:01Z · Confidence: high

Hunt Hypothesis

This hunt targets the presence of known Indicators of Compromise (IOCs) associated with the “stealler” malware family, which is designed to exfiltrate sensitive data such as credentials and browser information. Proactively hunting for these IOCs in Azure Sentinel allows the SOC to identify compromised endpoints or cloud assets before the adversary can successfully extract and leverage stolen secrets for lateral movement or privilege escalation.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hash2b8ed70633be6e539cbdf7ac60b770aece2442c8payload2026-09-0695%
md5_hash1eeb3ebf665197ce9a35fc1ac745c118payload2026-09-0695%
sha256_hashedd33db4a56d62fc653f67fc589d3421a2ce6678b4a28f85077f9200d8f2ea8bpayload2026-09-0695%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - stealler
let malicious_hashes = dynamic(["2b8ed70633be6e539cbdf7ac60b770aece2442c8", "1eeb3ebf665197ce9a35fc1ac745c118", "edd33db4a56d62fc653f67fc589d3421a2ce6678b4a28f85077f9200d8f2ea8b"]);
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/py.stealler/