This hunt hypothesis targets adversaries deploying Vidar malware to stealthily exfiltrate banking credentials and system data via encrypted channels following initial access through phishing or compromised web vectors. Proactively hunting for these indicators in Azure Sentinel is critical due to the high severity of potential financial loss and identity compromise, enabling early detection before sensitive data is fully extracted from the environment.
Malware Family: Vidar Total IOCs: 17 IOC Types: url, domain
| Type | Value | Threat Type | First Seen | Confidence |
|---|---|---|---|---|
| url | hxxps://aware-cr1.com/api/beacon | botnet_cc | 2026-08-11 | 100% |
| domain | wts.tb88vip.top | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://wts.tb88vip.top | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://45[.]86[.]245[.]217 | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://193[.]233[.]139[.]123 | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://91[.]92[.]242[.]142 | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://5[.]75[.]212[.]195 | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://167[.]233[.]197[.]223 | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://167[.]233[.]133[.]101 | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://167[.]233[.]137[.]121 | botnet_cc | 2026-08-11 | 100% |
| domain | dum.tb88soul.top | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://dum.tb88soul.top | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://91[.]98[.]108[.]158 | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://91[.]98[.]98[.]86 | botnet_cc | 2026-08-11 | 100% |
| domain | kwt.tb88roki.top | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://kwt.tb88roki.top | botnet_cc | 2026-08-11 | 100% |
| url | hxxps://78[.]40[.]209[.]22 | botnet_cc | 2026-08-11 | 100% |
// Hunt for DNS queries to known malicious domains
// Source: ThreatFox - Vidar
let malicious_domains = dynamic(["wts.tb88vip.top", "dum.tb88soul.top", "kwt.tb88roki.top"]);
DnsEvents
| where Name has_any (malicious_domains)
| project TimeGenerated, Computer, Name, IPAddresses, QueryType
| order by TimeGenerated desc
// Hunt for access to known malicious URLs
// Source: ThreatFox - Vidar
let malicious_urls = dynamic(["https://aware-cr1.com/api/beacon", "https://wts.tb88vip.top", "https://45.86.245.217", "https://193.233.139.123", "https://91.92.242.142", "https://5.75.212.195", "https://167.233.197.223", "https://167.233.133.101", "https://167.233.137.121", "https://dum.tb88soul.top", "https://91.98.108.158", "https://91.98.98.86", "https://kwt.tb88roki.top", "https://78.40.209.22"]);
UrlClickEvents
| where Url has_any (malicious_urls)
| project Timestamp, AccountUpn, Url, ActionType, IsClickedThrough
| order by Timestamp desc
| Sentinel Table | Notes |
|---|---|
DnsEvents | Ensure this data connector is enabled |
UrlClickEvents | Ensure this data connector is enabled |
Here are 5 specific false positive scenarios for the ThreatFox: Vidar IOCs detection rule, including suggested filters and exclusions tailored for an enterprise environment:
Scenario: Legitimate Phishing Simulation Campaigns
10.20.50.x for KnowBe4) or filter based on specific User-Agent strings containing “Phishing-Simulation” in the HTTP header.Scenario: Scheduled Backup and Credential Archiving Jobs
svc_backup_admin) or exclude network flows where the destination port is a known backup protocol port (e.g., TCP 9403 for Veeam) and the source process hash matches the trusted backup suite.Scenario: Automated Software Deployment via Endpoint Management