← Back to SOC feed Coverage →

ThreatFox: WannaCryptor IOCs

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

Hunt Hypothesis

This detection rule identifies WannaCryptor ransomware activity by monitoring for specific IOCs associated with phishing-delivered payloads that trigger mass file encryption across infected endpoints. SOC teams should proactively hunt for these indicators in Azure Sentinel to detect early-stage lateral movement and anomalous network traffic, enabling rapid containment before the malware spreads and demands ransom payments.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha256_hash381ab629fd8f5590643cbc93d9527038da1bc8aeef8ab1c7c2fada6a53be363apayload2026-08-2595%
sha1_hash518758f0de6d8969f456aafc46029bc9cbada419payload2026-08-2595%
md5_hash1d011399cbf80ab0970a15c6c07868d9payload2026-08-2595%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - WannaCryptor
let malicious_hashes = dynamic(["381ab629fd8f5590643cbc93d9527038da1bc8aeef8ab1c7c2fada6a53be363a", "518758f0de6d8969f456aafc46029bc9cbada419", "1d011399cbf80ab0970a15c6c07868d9"]);
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 5 specific false positive scenarios for the ThreatFox: WannaCryptor IOCs detection rule, including targeted filters and exclusions:

Original source: https://threatfox.abuse.ch/browse/malware/win.wannacryptor/