This hunt targets adversary behavior where QvoidStealer malware establishes initial footholds by leveraging specific known indicators of compromise to exfiltrate sensitive data from endpoints. Proactively hunting for these IOCs within Azure Sentinel is critical because early detection enables rapid containment before the stealer can propagate laterally or escalate privileges across the cloud environment.
Malware Family: QvoidStealer Total IOCs: 3 IOC Types: md5_hash, sha256_hash, sha1_hash
| Type | Value | Threat Type | First Seen | Confidence |
|---|---|---|---|---|
| md5_hash | 50cf5b4eb0b43d08455a381b05f4a4d3 | payload | 2026-07-13 | 95% |
| sha256_hash | 34ad97945a1f70cdbf8af7777a6c71c990d841840cf3c94a387f6cc83450ad4b | payload | 2026-07-13 | 95% |
| sha1_hash | 63000ff3aa0958801d3549446c7853f0d0223bcf | payload | 2026-07-13 | 95% |
// Hunt for files matching known malicious hashes
// Source: ThreatFox - QvoidStealer
let malicious_hashes = dynamic(["50cf5b4eb0b43d08455a381b05f4a4d3", "34ad97945a1f70cdbf8af7777a6c71c990d841840cf3c94a387f6cc83450ad4b", "63000ff3aa0958801d3549446c7853f0d0223bcf"]);
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
| Sentinel Table | Notes |
|---|---|
DeviceFileEvents | Ensure this data connector is enabled |
Here are specific false positive scenarios for the ThreatFox: QvoidStealer IOCs detection rule, tailored for an enterprise environment where legitimate activities may mimic the behavior of this stealer malware:
Endpoint Protection Policy Updates via Admin Console
Security-Management-Srv01) or filter out events where the Process Name is the known security agent service (e.g., CSPService.exe or MsMpEng.exe) running under a system account, provided the action is “Policy Update” or “Signature Download.”Enterprise Software Deployment via SCCM/Intune
ccmexec.exe (SCCM) or IntuneManagementExtension.exe, and the File Path resides within the standard deployment directories (e.g., C:\Windows\CCMCache\ or C:\Program Files\Microsoft Intune Management Extension\).Automated Compliance Scanning by Internal Audit Tools *