← 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-15T23:00:00Z · Confidence: high

Hunt Hypothesis

The ThreatFox: Mirai IOCs rule detects potential Mirai botnet activity by identifying known command-and-control servers and compromised devices commonly associated with this malware. SOC teams should proactively hunt for these indicators in Azure Sentinel to identify and mitigate Mirai-based botnet infections before they can cause widespread network disruption.

IOC Summary

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

TypeValueThreat TypeFirst SeenConfidence
ip:port192[.]159[.]99[.]110:2049payload_delivery2026-06-15100%
ip:port124[.]198[.]131[.]252:2049payload_delivery2026-06-15100%
ip:port92[.]42[.]100[.]131:4568payload_delivery2026-06-15100%

KQL: Ip Hunt

// Hunt for network connections to known malicious IPs
// Source: ThreatFox - Mirai
let malicious_ips = dynamic(["192.159.99.110", "92.42.100.131", "124.198.131.252"]);
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(["192.159.99.110", "92.42.100.131", "124.198.131.252"]);
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/