← Back to SOC feed Coverage →

ThreatFox: HypeAgent IOCs

ioc-hunt HIGH ThreatFox
CommonSecurityLogDeviceNetworkEvents
iocthreatfoxwin-hype_agent
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-08-20T23:00:00Z · Confidence: high

Hunt Hypothesis

This detection rule identifies adversary activity by matching network and endpoint logs against known Indicators of Compromise (IOCs) specific to the HypeAgent threat actor within Azure Sentinel. Proactively hunting for these IOCs is critical because early identification of HypeAgent’s unique signatures allows the SOC team to rapidly isolate affected assets and mitigate potential lateral movement before broader compromise occurs.

IOC Summary

Malware Family: HypeAgent Total IOCs: 18 IOC Types: ip:port

TypeValueThreat TypeFirst SeenConfidence
ip:port95[.]164[.]123[.]132:7443botnet_cc2026-08-2075%
ip:port45[.]141[.]215[.]40:7443botnet_cc2026-08-2075%
ip:port217[.]217[.]97[.]125:7443botnet_cc2026-08-2075%
ip:port147[.]124[.]221[.]0:62020botnet_cc2026-08-2075%
ip:port95[.]164[.]123[.]132:53105botnet_cc2026-08-2075%
ip:port95[.]164[.]123[.]132:56545botnet_cc2026-08-2075%
ip:port95[.]164[.]123[.]132:7080botnet_cc2026-08-2075%
ip:port91[.]92[.]47[.]94:7080botnet_cc2026-08-2075%
ip:port91[.]92[.]47[.]94:7443botnet_cc2026-08-2075%
ip:port91[.]124[.]98[.]25:7080botnet_cc2026-08-2075%
ip:port91[.]124[.]98[.]25:7443botnet_cc2026-08-2075%
ip:port45[.]141[.]215[.]40:7080botnet_cc2026-08-2075%
ip:port217[.]217[.]97[.]125:7080botnet_cc2026-08-2075%
ip:port213[.]152[.]186[.]188:32605botnet_cc2026-08-2075%
ip:port213[.]152[.]186[.]188:32635botnet_cc2026-08-2075%
ip:port192[.]109[.]139[.]69:7443botnet_cc2026-08-2075%
ip:port192[.]109[.]139[.]69:7080botnet_cc2026-08-2075%
ip:port104[.]168[.]70[.]163:7080botnet_cc2026-08-2075%

KQL: Ip Hunt

// Hunt for network connections to known malicious IPs
// Source: ThreatFox - HypeAgent
let malicious_ips = dynamic(["104.168.70.163", "192.109.139.69", "217.217.97.125", "91.92.47.94", "45.141.215.40", "213.152.186.188", "147.124.221.0", "91.124.98.25", "95.164.123.132"]);
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(["104.168.70.163", "192.109.139.69", "217.217.97.125", "91.92.47.94", "45.141.215.40", "213.152.186.188", "147.124.221.0", "91.124.98.25", "95.164.123.132"]);
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

Here are 5 specific false positive scenarios for the ThreatFox: HypeAgent IOCs detection rule, including suggested filters and exclusions tailored for an enterprise environment:

Original source: https://threatfox.abuse.ch/browse/malware/win.hype_agent/