← Back to SOC feed Coverage →

ThreatFox: Akira Stealer IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
infostealeriocpy-akira_stealerthreatfox
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-05T23:00:00Z · Confidence: high

Hunt Hypothesis

This hunt targets the presence of Akira Stealer IOCs to identify compromised endpoints where this infostealer is actively harvesting credentials, browser data, and cryptocurrency wallet information. Proactively hunting for these indicators in Azure Sentinel allows the SOC to detect and isolate infections early, preventing the exfiltration of sensitive data and lateral movement before the adversary establishes a persistent foothold.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
sha256_hashc42e431a727120c9da477c32f1ffe0b5ac46805ff7bc0516252da29a0d172bcdpayload2026-09-0595%
sha1_hash532749e27f6b9458b4390eed3fb3774ba4126f04payload2026-09-0595%
md5_hashf398eabde69bc3369038f987fcc17bd4payload2026-09-0595%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - Akira Stealer
let malicious_hashes = dynamic(["c42e431a727120c9da477c32f1ffe0b5ac46805ff7bc0516252da29a0d172bcd", "532749e27f6b9458b4390eed3fb3774ba4126f04", "f398eabde69bc3369038f987fcc17bd4"]);
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/py.akira_stealer/