← Back to SOC feed Coverage →

ThreatFox: KongTuke IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEventsDnsEvents
iocjs-kongtukethreatfox
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-04-24T09:00:00Z · Confidence: high

Hunt Hypothesis

The KongTuke malware is likely exfiltrating sensitive data through covert network communications, which can be detected by unusual outbound traffic patterns. SOC teams should proactively hunt for this behavior in Azure Sentinel to identify and mitigate data exfiltration attempts before significant data loss occurs.

IOC Summary

Malware Family: KongTuke Total IOCs: 2 IOC Types: sha256_hash, domain

TypeValueThreat TypeFirst SeenConfidence
domaindummy-tf-test-dummy-rfnsp2ni.examplepayload_delivery2026-04-2450%
sha256_hash6316e735a026e0421e4ee274e36594bb510afbf8798e767f6a082d827b5082a0payload2026-04-2490%

KQL: Domain Hunt

// Hunt for DNS queries to known malicious domains
// Source: ThreatFox - KongTuke
let malicious_domains = dynamic(["dummy-tf-test-dummy-rfnsp2ni.example"]);
DnsEvents
| where Name has_any (malicious_domains)
| project TimeGenerated, Computer, Name, IPAddresses, QueryType
| order by TimeGenerated desc

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - KongTuke
let malicious_hashes = dynamic(["6316e735a026e0421e4ee274e36594bb510afbf8798e767f6a082d827b5082a0"]);
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
DnsEventsEnsure this data connector is enabled

References

False Positive Guidance

Original source: https://threatfox.abuse.ch/browse/malware/js.kongtuke/