← Back to SOC feed Coverage →

ThreatFox: ToxicPanda IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
apk-toxic_pandaiocthreatfox
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-04T23:00:00Z · Confidence: high

Hunt Hypothesis

This hunt targets known indicators of compromise associated with the ToxicPanda threat actor, enabling the detection of their specific infrastructure or artifacts within the environment. Proactively hunting for these IOCs in Azure Sentinel is critical to identify potential footholds or lateral movement activities before the adversary can establish persistence or exfiltrate data.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
md5_hash86cdd96dd22dc0683f4214fe5bc80a53payload2026-09-0495%
sha256_hashde9c97e154274a3070b32cbcefa274b9be9fd626533e203cdd5b680d00ae65f7payload2026-09-0495%
sha1_hashbbe8e49d4fe1eb2daad3a1041e650f3a894695adpayload2026-09-0495%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - ToxicPanda
let malicious_hashes = dynamic(["86cdd96dd22dc0683f4214fe5bc80a53", "de9c97e154274a3070b32cbcefa274b9be9fd626533e203cdd5b680d00ae65f7", "bbe8e49d4fe1eb2daad3a1041e650f3a894695ad"]);
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/apk.toxic_panda/