← Back to SOC feed Coverage →

ThreatFox: TinyMet IOCs

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

Hunt Hypothesis

The ThreatFox: TinyMet IOCs rule detects potential adversary activity associated with the TinyMet malware, which is known for its persistence and data exfiltration capabilities. SOC teams should proactively hunt for this behavior in Azure Sentinel to identify and mitigate advanced threats that may be operating undetected within their environment.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hash96beaa210c51ebc95b19379dd9572013132e7c4dpayload2026-06-1795%
md5_hashae9613c81a644178999b357600d1498apayload2026-06-1795%
sha256_hashff0d872eb0f0474a24273ff2506b9c1e5e7c7ba5fa8d364cea94e0c7405d032cpayload2026-06-1795%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - TinyMet
let malicious_hashes = dynamic(["96beaa210c51ebc95b19379dd9572013132e7c4d", "ae9613c81a644178999b357600d1498a", "ff0d872eb0f0474a24273ff2506b9c1e5e7c7ba5fa8d364cea94e0c7405d032c"]);
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.tinymet/