Request to known malicious URL on 192.162.199.249

SIGhighconfidence 100/100generated 2026-10-18

Proxy request matching a URL tracked by skopnix as AMOS (delivery).

ATT&CK: T1105 mitre ↗
False positives: Scoped to one indicator with skopnix confidence 100/100 from 2 independent sources; checked against RFC1918/reserved space, CDN / cloud / scanner ranges and top-site lists (MISP warninglists), GreyNoise when enriched, and skopnix's benign-infrastructure list. Re-validate against last_seen before blocking: infrastructure is re-assigned.

Sigma rule

skopnix-sigma-ioc-url-http-192-162-199-249-hbspbloprxh3iu2h-8e8b6000.ymldownload .yml ↓

title: Skopnix - Request to known malicious URL on 192.162.199.249
id: a55e8fb3-5605-5f90-aa41-20cbdeb02d79
status: experimental
description: Proxy request matching a URL tracked by skopnix as AMOS (delivery).
references:
  - https://skopnix.com/ioc/http://192.162.199.249/hbspbloprxh3iu2h
author: skopnix
date: '2026-10-18'
tags:
  - attack.command-and-control
  - attack.t1105
logsource:
  category: proxy
detection:
  selection:
    cs-host: 192.162.199.249
    c-uri|contains: /hbspbloprxh3iu2h
  condition: selection
falsepositives:
  - Legitimate services sharing the address; verify against skopnix confidence + last_seen
level: high

How to deploy on Sigma

1.Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
2.Run it as a hunt first: every rule ships as status experimental.
3.Promote to an alert once a week of results is clean on your data.

Check · The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.

References

skopnix.com/ioc/http://192.162.199.249/hbspbloprxh3iu2h ↗