← Back to SOC feed Coverage →

ThreatFox: SVCStealer IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
infostealeriocthreatfoxwin-svcstealer
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-09-24T23:00:00Z · Confidence: high

Hunt Hypothesis

This hunt targets the presence of SVCStealer, a credential-stealing malware that often propagates via service control blocks, by correlating its known indicators of compromise against endpoint telemetry. Proactively hunting for these IOCs in Azure Sentinel is critical because SVCStealer can silently exfiltrate stored credentials and establish persistence, allowing adversaries to pivot laterally through the environment before traditional detections trigger.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha1_hash0eedde175f5d230ee129dc4add72be8a32e7c05apayload2026-09-2495%
md5_hashc705fea2fd2e6c119c1138f1b74cd798payload2026-09-2495%
sha256_hash221e2c855e78d5cc7fb84738effb88bb11a47be6ce10530c909534e15f47e0b4payload2026-09-2495%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - SVCStealer
let malicious_hashes = dynamic(["0eedde175f5d230ee129dc4add72be8a32e7c05a", "c705fea2fd2e6c119c1138f1b74cd798", "221e2c855e78d5cc7fb84738effb88bb11a47be6ce10530c909534e15f47e0b4"]);
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.svcstealer/