← Back to SOC feed Coverage →

ThreatFox: Vidar IOCs

ioc-hunt HIGH ThreatFox
UrlClickEvents
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-07-19T11:00:00Z · Confidence: high

Hunt Hypothesis

This hypothesis posits that adversaries are leveraging Vidar malware to establish persistence and exfiltrate sensitive data through known indicators of compromise within the Azure environment. The SOC team should proactively hunt for these specific IOCs in Azure Sentinel to rapidly identify early-stage infections before they escalate into broader lateral movement or data theft incidents.

IOC Summary

Malware Family: Vidar Total IOCs: 2 IOC Types: url

TypeValueThreat TypeFirst SeenConfidence
urlhxxps://afsd.net/payload_delivery2026-07-1975%
urlhxxps://kayhector.com/payload_delivery2026-07-1975%

KQL: Url Hunt

// Hunt for access to known malicious URLs
// Source: ThreatFox - Vidar
let malicious_urls = dynamic(["https://afsd.net/", "https://kayhector.com/"]);
UrlClickEvents
| where Url has_any (malicious_urls)
| project Timestamp, AccountUpn, Url, ActionType, IsClickedThrough
| order by Timestamp desc

Required Data Sources

Sentinel TableNotes
UrlClickEventsEnsure this data connector is enabled

References

False Positive Guidance

Here are specific false positive scenarios for the ThreatFox: Vidar IOCs detection rule in an enterprise environment, along with suggested filters and exclusions:

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