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

Hunt Hypothesis

This hunt hypothesis targets adversary behavior where WannaCryptor ransomware executes known indicators of compromise to encrypt critical data and disrupt operations within the environment. Proactively hunting for these specific IOCs in Azure Sentinel is essential to enable early detection before widespread encryption occurs, thereby minimizing downtime and accelerating incident response times.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hash57ccec59ebeb2aecbc045d01853412ca2b1c3e0epayload2026-07-1095%
md5_hashdc614bc8781cb85e4ddf2bbb7860cb84payload2026-07-1095%
sha256_hashe4846ec6171f65e96c2909ad93359451551e3ac95aa89ab349d5ab773cbaa0d6payload2026-07-1095%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - WannaCryptor
let malicious_hashes = dynamic(["57ccec59ebeb2aecbc045d01853412ca2b1c3e0e", "dc614bc8781cb85e4ddf2bbb7860cb84", "e4846ec6171f65e96c2909ad93359451551e3ac95aa89ab349d5ab773cbaa0d6"]);
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 for the ThreatFox: WannaCryptor IOCs detection rule in an enterprise environment, along with suggested filters or exclusions:


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