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

Hunt Hypothesis

This detection rule identifies adversary activity involving specific Indicators of Compromise (IOCs) linked to the Stealer malware family, which is known for exfiltrating sensitive credentials and financial data from compromised endpoints. The SOC team should proactively hunt for these IOCs within Azure Sentinel to rapidly detect early-stage infections and prevent potential lateral movement or data breaches before the threat escalates.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
md5_hash11b388e073236318b3851c168aa1abdepayload2026-08-0895%
sha256_hash254412f2ca69b69f8b686f874374e2584aaf55ad5c3e8ed6eddfa69f3fe6ea2bpayload2026-08-0895%
sha1_hash3b2ce84bea55b35c195a046f40dd838931960270payload2026-08-0895%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - stealler
let malicious_hashes = dynamic(["11b388e073236318b3851c168aa1abde", "254412f2ca69b69f8b686f874374e2584aaf55ad5c3e8ed6eddfa69f3fe6ea2b", "3b2ce84bea55b35c195a046f40dd838931960270"]);
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

Here are the false positive scenarios and corresponding exclusions for the ThreatFox: stealler IOCs detection rule:

Original source: https://threatfox.abuse.ch/browse/malware/py.stealler/