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

Hunt Hypothesis

This hunt targets adversary behavior consistent with the WannaCryptor ransomware campaign by actively searching for its specific indicators of compromise across the environment. Proactively hunting for these IOCs in Azure Sentinel is critical to enable early detection and rapid containment before the malware can execute its encryption payload and disrupt business operations.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hash161a0dc51f1dd79421194ab79236159ae994f688payload2026-07-0595%
md5_hash342f8fe9a988cbdb27f7756a2754549dpayload2026-07-0595%
sha256_hashfc772ded09936960f85abe63e2162ac141d072eeb60d3f5a4c0e47f249c9b6a9payload2026-07-0595%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - WannaCryptor
let malicious_hashes = dynamic(["161a0dc51f1dd79421194ab79236159ae994f688", "342f8fe9a988cbdb27f7756a2754549d", "fc772ded09936960f85abe63e2162ac141d072eeb60d3f5a4c0e47f249c9b6a9"]);
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 4 specific false positive scenarios for the ThreatFox: WannaCryptor IOCs detection rule, including suggested filters and exclusions tailored for an enterprise environment:

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