← 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-13T23:00:00Z · 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 harvesting credentials and sensitive data from compromised endpoints. SOC teams should proactively hunt for these IOCs within Azure Sentinel to rapidly detect early-stage infections and prevent lateral movement before attackers can exfiltrate critical assets.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hash2794280875a99f47ddcf347f3eaa5f57ecc30058payload2026-08-1395%
md5_hash757b7e2991187e4644f8092801547730payload2026-08-1395%
sha256_hash664f8e49f45b3fda22f2deb4a164e9dd0737cd8ec65aef928526b86424bb3726payload2026-08-1395%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - stealler
let malicious_hashes = dynamic(["2794280875a99f47ddcf347f3eaa5f57ecc30058", "757b7e2991187e4644f8092801547730", "664f8e49f45b3fda22f2deb4a164e9dd0737cd8ec65aef928526b86424bb3726"]);
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 specific false positive scenarios and corresponding exclusion strategies for the ThreatFox: stealler IOCs detection rule in an enterprise environment:

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