← Back to SOC feed Coverage →

ThreatFox: Kuiper IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
elf-kuiperiocthreatfox
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-07-30T23:00:00Z · Confidence: high

Hunt Hypothesis

This hunt hypothesis detects adversary activity by correlating network and endpoint telemetry against eleven specific Indicators of Compromise (IOCs) linked to the Kuiper threat cluster. Proactively hunting for these IOCs within Azure Sentinel is critical because early identification of known malicious artifacts enables rapid containment before adversaries can establish persistence or exfiltrate sensitive data.

IOC Summary

Malware Family: Kuiper Total IOCs: 11 IOC Types: md5_hash, sha1_hash, sha256_hash

TypeValueThreat TypeFirst SeenConfidence
sha1_hash0664d2922ea22920f609f17e3f5b512623d940b5payload2026-07-3095%
md5_hashaf38775c7c7dc7046f77a7748b89933dpayload2026-07-3095%
sha256_hash27550b8c15c5a7cf5568dd1d2e1243b510eb983a7eb8ff5ddc9974415e5a0093payload2026-07-3095%
sha1_hash58ab34482258c4b7f1c8e1f7e5b71d93060117a0payload2026-07-3095%
md5_hash63951c4114bb7b172c40a8d72f1571ebpayload2026-07-3095%
sha256_hashe0968fdd46a966fd96963e0c082c826f0f4f68c6ae7c47db740e375b838a5166payload2026-07-3095%
md5_hashfb52e944c7d2c7ef88c1fa2bc49bca8dpayload2026-07-3095%
sha256_hasha698fd443f31acb8747f8f8a33460eb04952bf3437ff0e07236207acace850e8payload2026-07-3095%
sha1_hash2cbd1b25814007055d72bb2373ae5d3a15f6f891payload2026-07-3095%
sha1_hash69959abe409438a3f0a7b5a48c6ee0eba89e52f2payload2026-07-3095%
md5_hash7e156047d9217122c15da13f2c8765a5payload2026-07-3095%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - Kuiper
let malicious_hashes = dynamic(["0664d2922ea22920f609f17e3f5b512623d940b5", "af38775c7c7dc7046f77a7748b89933d", "27550b8c15c5a7cf5568dd1d2e1243b510eb983a7eb8ff5ddc9974415e5a0093", "58ab34482258c4b7f1c8e1f7e5b71d93060117a0", "63951c4114bb7b172c40a8d72f1571eb", "e0968fdd46a966fd96963e0c082c826f0f4f68c6ae7c47db740e375b838a5166", "fb52e944c7d2c7ef88c1fa2bc49bca8d", "a698fd443f31acb8747f8f8a33460eb04952bf3437ff0e07236207acace850e8", "2cbd1b25814007055d72bb2373ae5d3a15f6f891", "69959abe409438a3f0a7b5a48c6ee0eba89e52f2", "7e156047d9217122c15da13f2c8765a5"]);
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

Here are 3-5 specific false positive scenarios for the ThreatFox: Kuiper IOCs detection rule, along with targeted filtering strategies suitable for an enterprise environment:

Original source: https://threatfox.abuse.ch/browse/malware/elf.kuiper/