This hunt targets the presence of 11 known Indicators of Compromise (IOCs) associated with the Remus threat actor, which may indicate an active intrusion or persistent foothold within the environment. Proactively hunting for these specific IOCs in Azure Sentinel allows the SOC team to identify and isolate compromised assets before the adversary can leverage them for lateral movement or data exfiltration.
Malware Family: Remus Total IOCs: 11 IOC Types: url
| Type | Value | Threat Type | First Seen | Confidence |
|---|---|---|---|---|
| url | hxxp://boltore.click:7652/tasks | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://phetsre.shop:3452/sessions | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://fgashub.shop:9932/customers | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://phetsre.shop:3452/posts | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://hkealop.shop:9932/documents | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://alutove.shop:5627/tags | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://homecor.click:6527/posts | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://hkealop.shop:9932/orders | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://alutove.shop:5627/subscriptions | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://kipthen.shop:9932/articles | botnet_cc | 2026-09-21 | 75% |
| url | hxxp://tfoyses.shop:3452/permissions | botnet_cc | 2026-09-21 | 75% |
// Hunt for access to known malicious URLs
// Source: ThreatFox - Remus
let malicious_urls = dynamic(["http://boltore.click:7652/tasks", "http://phetsre.shop:3452/sessions", "http://fgashub.shop:9932/customers", "http://phetsre.shop:3452/posts", "http://hkealop.shop:9932/documents", "http://alutove.shop:5627/tags", "http://homecor.click:6527/posts", "http://hkealop.shop:9932/orders", "http://alutove.shop:5627/subscriptions", "http://kipthen.shop:9932/articles", "http://tfoyses.shop:3452/permissions"]);
UrlClickEvents
| where Url has_any (malicious_urls)
| project Timestamp, AccountUpn, Url, ActionType, IsClickedThrough
| order by Timestamp desc
| Sentinel Table | Notes |
|---|---|
UrlClickEvents | Ensure this data connector is enabled |
Scenario: The Remus IOC set includes known IP addresses or domain names that are part of the enterprise’s internal load balancer infrastructure or third-party SaaS provider endpoints (e.g., a specific *.remus.io subdomain used by a niche CI/CD tool or a legacy monitoring agent).
10.0.0.0/8 or 172.16.0.0/12 ranges, or specifically exclude the known SaaS provider’s ASN (e.g., AS15169 for Google Cloud) if the IOC matches a public cloud endpoint.Scenario: A scheduled maintenance job on a Linux build server uses a script that downloads a dependency package from a repository whose hostname matches one of the Remus IOCs (e.g., a generic remus-packages.com domain used by a niche open-source library).
curl, wget, or python and the parent process is a known build tool like jenkins-agent, gitlab-runner, or ansible-playbook, and the destination port is 443.Scenario: An endpoint detection agent (such as CrowdStrike or SentinelOne) performs a self-update or fetches a configuration blob from a CDN whose IP address coincidentally matches one of the static IP IOCs in the Remus set.
FalconSensor.exe, SentinelOneAgent.exe, or osqueryd) and the destination port is 443 or 80.Scenario: A developer’s laptop connects to a staging