Request to known malicious URL on officemysuppbox.com

SIGmediumconfidence 77/100generated 2026-10-18

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

ATT&CK: T1105 mitre ↗
Linked actors: TA505
False positives: Scoped to one indicator with skopnix confidence 77/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-officemysuppbox-com-staterepository-06f4718d.ymldownload .yml ↓

title: Skopnix - Request to known malicious URL on officemysuppbox.com
id: 8f0c62de-25b8-579e-bd7e-1f880e55b1d0
status: experimental
description: Proxy request matching a URL tracked by skopnix as malware_download (delivery).
references:
  - https://skopnix.com/ioc/http://officemysuppbox.com/staterepository
author: skopnix
date: '2026-10-18'
tags:
  - attack.command-and-control
  - attack.t1105
logsource:
  category: proxy
detection:
  selection:
    cs-host: officemysuppbox.com
    c-uri|contains: /staterepository
  condition: selection
falsepositives:
  - Legitimate services sharing the address; verify against skopnix confidence + last_seen
level: medium

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://officemysuppbox.com/staterepository ↗