ThreatFox: Aisuru IOCs | SOC Hunt Feed

Hunt Hypothesis

This hunt identifies potential compromise by matching network traffic and asset data against known indicators of compromise associated with the Aisuru threat actor. Proactively hunting for these IOCs in Azure Sentinel allows the SOC team to detect lateral movement or command-and-control activity before the adversary can establish a persistent foothold or exfiltrate sensitive data.

IOC Summary

Malware Family: Aisuru Total IOCs: 10 IOC Types: ip:port

Type	Value	Threat Type	First Seen	Confidence
ip:port	`161[.]35[.]166[.]196:8001`	botnet_cc	2026-09-09	100%
ip:port	`138[.]68[.]130[.]69:8001`	botnet_cc	2026-09-09	100%
ip:port	`159[.]65[.]59[.]117:8001`	botnet_cc	2026-09-09	100%
ip:port	`165[.]22[.]113[.]73:8001`	botnet_cc	2026-09-09	100%
ip:port	`64[.]225[.]102[.]231:8001`	botnet_cc	2026-09-09	100%
ip:port	`139[.]59[.]143[.]6:8001`	botnet_cc	2026-09-09	75%
ip:port	`164[.]92[.]207[.]173:8001`	botnet_cc	2026-09-09	75%
ip:port	`165[.]227[.]142[.]229:8001`	botnet_cc	2026-09-09	100%
ip:port	`209[.]38[.]225[.]90:8001`	botnet_cc	2026-09-09	100%
ip:port	`139[.]59[.]168[.]101:8001`	botnet_cc	2026-09-09	100%

KQL: Ip Hunt

// Hunt for network connections to known malicious IPs
// Source: ThreatFox - Aisuru
let malicious_ips = dynamic(["159.65.59.117", "165.22.113.73", "164.92.207.173", "161.35.166.196", "64.225.102.231", "138.68.130.69", "209.38.225.90", "139.59.168.101", "165.227.142.229", "139.59.143.6"]);
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(["159.65.59.117", "165.22.113.73", "164.92.207.173", "161.35.166.196", "64.225.102.231", "138.68.130.69", "209.38.225.90", "139.59.168.101", "165.227.142.229", "139.59.143.6"]);
DeviceNetworkEvents
| where RemoteIP in (malicious_ips)
| project Timestamp, DeviceName, RemoteIP, RemotePort, InitiatingProcessFileName, ActionType
| order by Timestamp desc

Required Data Sources

Sentinel Table	Notes
`CommonSecurityLog`	Ensure this data connector is enabled
`DeviceNetworkEvents`	Ensure this data connector is enabled

References

ThreatFox — Aisuru

False Positive Guidance

Scenario: A legacy application server running an outdated version of Apache Tomcat or a specific Java-based web framework that contains a known vulnerable dependency (e.g., log4j or a specific commons-collections version) which matches one of the Aisuru IOCs (such as specific file hashes or registry keys associated with initial access vectors).
- Filter/Exclusion: Exclude processes originating from specific service accounts (e.g., svc-tomcat, app-pool) or exclude file paths under standard application directories (e.g., C:\Program Files\Apache Tomcat\, C:\inetpub\wwwroot\) if the IOC is a file hash or path-based.
Scenario: An IT administrator performing a routine patching or software deployment task using a tool like SCCM (System Center Configuration Manager) or PDQ Deploy, where the deployment package includes a binary or script that matches an Aisuru IOC (e.g., a specific rundll32 command line pattern or a known vulnerable DLL hash) due to the software being in a pre-patch state.
- Filter/Exclusion: Exclude events where the parent process is a known deployment tool (e.g., ccmexec.exe, pdqdeploy.exe) or where the command line contains specific deployment identifiers (e.g., /install, /update, sccm).
Scenario: A developer or QA engineer running a local test environment or a containerized application (e.g., Docker, Kubernetes) that uses a base image or library containing a known Aisuru-associated IOC (e.g., a specific wget or curl user-agent string, or a known vulnerable library version) for testing purposes.
- Filter/Exclusion: Exclude processes running from container runtimes (e.g., dockerd.exe, containerd.exe) or