← Back to SOC feed Coverage →

ThreatFox: Vidar IOCs

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

Hunt Hypothesis

The ThreatFox: Vidar IOCs rule detects potential command and control activity associated with the Vidar malware, leveraging known indicators to identify compromised systems. SOC teams should proactively hunt for this behavior in Azure Sentinel to mitigate lateral movement and data exfiltration risks early in the attack lifecycle.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha256_hashd0d8d45ef06d0d9ee5f3e0b01885c965f8541d2ad0cba3ca401aca56bb0258e9payload2026-06-2695%
sha1_hashccad36f947b504ab0d3fa44db56416bbeba001fepayload2026-06-2695%
md5_hash5eca7be606723c470d02afbb53188dc2payload2026-06-2695%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - Vidar
let malicious_hashes = dynamic(["d0d8d45ef06d0d9ee5f3e0b01885c965f8541d2ad0cba3ca401aca56bb0258e9", "ccad36f947b504ab0d3fa44db56416bbeba001fe", "5eca7be606723c470d02afbb53188dc2"]);
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

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