← Back to SOC feed Coverage →

ThreatFox: Mirai IOCs

ioc-hunt HIGH ThreatFox
CommonSecurityLogDeviceNetworkEvents
elf-miraiiocthreatfox
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-06-14T23:00:00Z · Confidence: high

Hunt Hypothesis

The ThreatFox: Mirai IOCs rule detects potential Mirai botnet activity by identifying known malicious indicators associated with command-and-control communication and distributed denial-of-service attacks. SOC teams should proactively hunt for this behavior in Azure Sentinel to identify and mitigate early-stage Mirai infections before they cause widespread network disruption.

IOC Summary

Malware Family: Mirai Total IOCs: 3 IOC Types: ip:port

TypeValueThreat TypeFirst SeenConfidence
ip:port5[.]39[.]216[.]137:8083payload_delivery2026-06-14100%
ip:port5[.]39[.]216[.]137:8082payload_delivery2026-06-14100%
ip:port5[.]175[.]215[.]102:456payload_delivery2026-06-14100%

KQL: Ip Hunt

// Hunt for network connections to known malicious IPs
// Source: ThreatFox - Mirai
let malicious_ips = dynamic(["5.39.216.137", "5.175.215.102"]);
CommonSecurityLog
| where DestinationIP in (malicious_ips) or SourceIP in (malicious_ips)
| project TimeGenerated, SourceIP, DestinationIP, DestinationPort, DeviceAction, Activity
| order by TimeGenerated desc

KQL: Ip Hunt Device

// Hunt in Defender for Endpoint network events
let malicious_ips = dynamic(["5.39.216.137", "5.175.215.102"]);
DeviceNetworkEvents
| where RemoteIP in (malicious_ips)
| project Timestamp, DeviceName, RemoteIP, RemotePort, InitiatingProcessFileName, ActionType
| order by Timestamp desc

Required Data Sources

Sentinel TableNotes
CommonSecurityLogEnsure this data connector is enabled
DeviceNetworkEventsEnsure this data connector is enabled

References

False Positive Guidance

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