← Back to SOC feed Coverage →

ThreatFox: Amadey IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
iocthreatfoxwin-amadey
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-13T11:00:00Z · Confidence: high

Hunt Hypothesis

The ThreatFox: Amadey IOCs rule detects potential adversary activity linked to the Amadey malware, which is associated with advanced persistent threats and data exfiltration. SOC teams should proactively hunt for this behavior in Azure Sentinel to identify and mitigate early-stage compromise and prevent data loss.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hash1d3a5e780488095d6174bcdc49ee16c0ea802a6apayload2026-06-1395%
md5_hash347187dc7824a887b8f6a3272b3baf12payload2026-06-1395%
sha256_hash49999f257686cfba6fe9504ff99a7776f998e3ba4887d28d2957f040ac346306payload2026-06-1395%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - Amadey
let malicious_hashes = dynamic(["1d3a5e780488095d6174bcdc49ee16c0ea802a6a", "347187dc7824a887b8f6a3272b3baf12", "49999f257686cfba6fe9504ff99a7776f998e3ba4887d28d2957f040ac346306"]);
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.amadey/